safe_export_policy
MCP server · Local · nothing leaves your machine
The keep and drop tables verbatim, for a security reviewer who would rather read the rules than infer them from a generated query.
Scrub the direct identifiers before the data leaves, then trial on the scrubbed file. A dataset that never contained direct identifiers usually does not need an infosec review, a DPA, or procurement, so you can evaluate on real data without asking anyone permission first.
What it returns
The keep and drop tables in full - every column role that may leave the org with the transform it needs, every column that never may and why, and the guidance on how much history to export.
Credential
None. This tool runs entirely inside the agent: it makes no network call, needs no credential, and sends none of what you pass it anywhere.
Network call: no. The full credential split is on authentication.
Example call
Most readers never write the protocol themselves: the agent does, once the server is connected. Both forms are the same call.
Use the ax1om MCP server.Call safe_export_policy: the keep and drop tables verbatim, for a security reviewer who would rather read the rules than infer them from a generated query.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "safe_export_policy", "arguments": {} }}The arguments object is whatever this tool's own input schema declares. An MCP client reads that schema from the server, so it is the server that answers for the exact shape rather than this page.