account_export
Export this account's own data across every table the account owns, as the same JSON envelope the REST route returns. The set of tables served is derived from the same ownership reflection that decides what an account deletion removes, so a table the account can destroy is a table it can also rea...
This record as markdown: /tools/com-meta-council-decision-intelligence/account-export.md
What account_export does on Meta Council
AI agents call account_export to permanently remove resources in Meta Council, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
models | array | — | Model names to narrow to, which is how a caller pages a table that truncated without re-reading the others. Omit to export every model the coverage block lists |
rows_per_model | integer | — | Row ceiling applied to each model separately. Defaults to 500, maximum 5000. |
Parameters from the server's own tool schema.
Why account_export is rated Critical
An AI agent that decides to call account_export doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Meta Council is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs account_export safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For account_export, this is the rule to start with:
account_export is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every account_export call is checked against it from then on.
Questions about account_export
Export this account's own data across every table the account owns, as the same JSON envelope the REST route returns. The set of tables served is derived from the same ownership reflection that decides what an account deletion removes, so a table the account can destroy is a table it can also read. Credentials never appear: columns held encrypted at rest are withheld unless recorded as the account's own content, and password hashes, reset and verification tokens, and API key hashes are withheld by name. Some tables are deliberately excluded -- see docs/ACCOUNT_DATA_EXPORT.md, and note that the coverage block on every response lists exactly which models are served and which are excluded with their reasons. Artifacts are described by their metadata rows rather than inlined. Bounded rather than streamed: each model reports truncated and the envelope reports complete, so narrow to one model and raise rows_per_model rather than re-reading everything. This is a data export, not an erasure request and not a claim of regulatory compliance. Requires authentication and the account:export scope. It is categorised as a Destructive tool in the Meta Council MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
account_export accepts 2 parameters: models, rows_per_model. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for account_export: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Meta Council. Nothing to install.
account_export is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the account_export rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for account_export. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
account_export is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
Across the catalogue