audit_export

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/audit-export.md

WHAT IT DOES

What audit_export does on Meta Council

AI agents use audit_export to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.

Parameter	Type	Required	Description
`limit`	integer	—	Events per page. Defaults to 100, maximum 500.
`since`	string	—	ISO-8601 lower bound, inclusive, for example 2026-08-01T00:00:00Z. Omit for no lower bound.
`until`	string	—	ISO-8601 upper bound, inclusive. Omit for no upper bound.
`action`	string	—	Exact event action to filter to, for example mcp.tool_call. Omit to return every action this workspace can export.
`after_id`	integer	—	Resume cursor. Pass the next_cursor from the previous page to continue without re-reading it.

Parameters from the server's own tool schema.

RISK

Why audit_export is rated Medium

An AI agent can call audit_export faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs audit_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 audit_export, this is the rule to start with:

audit_export Rate-limited

audit_export stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "audit_export": {
      "limits": [
        {
          "counter": "audit_export_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every audit_export call is checked against it from then on.

FAQ

Questions about audit_export

What does the audit_export tool do? +

Export this workspace's own agent-action audit trail as structured events, oldest first, for loading into a SIEM. Each event carries what triggered the action, which identity authorized it, which resource was touched, the outcome, and the error state. Metadata only -- no prompt text, document content, tool arguments, or model output is ever returned. Filter by date range and event action; page forward with the cursor each response returns. Covers a documented subset of platform activity rather than every action: see docs/WORKSPACE_AUDIT_EXPORT.md, and note that the coverage block on every response lists exactly which actions are exportable and which are not. Requires authentication and the audit:read scope. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does audit_export accept? +

audit_export accepts 5 parameters: limit, since, until, action, after_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on audit_export? +

Register the Meta Council MCP server in PolicyLayer and add a rule for audit_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.

What risk level is audit_export? +

audit_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit audit_export? +

Yes. Add a rate_limit block to the audit_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.

How do I block audit_export completely? +

Set action: deny in the PolicyLayer policy for audit_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.

What MCP server provides audit_export? +

audit_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.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →