list_accounting_runs
List only the caller's private Accounting-run audit metadata, newest first. Raw source text and analysis results are intentionally omitted.
This record as markdown: /tools/com-meta-council-decision-intelligence/list-accounting-runs.md
What list_accounting_runs does on Meta Council
AI agents call list_accounting_runs to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
offset | integer | — | |
status | string | — |
Parameters from the server's own tool schema.
Why list_accounting_runs is rated Low
This tool retrieves and queries audit metadata without modifying, deleting, or executing any operations. It is scoped to the caller's private data only and explicitly excludes detailed source material, making it a straightforward Read operation with low severity—it cannot affect system state or cause harm through misuse.
From the tool's definition Tool name contains 'list' and description explicitly states it 'List only the caller's private Accounting-run audit metadata' with 'Raw source text and analysis results are intentionally omitted.' This is a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_accounting_runs 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 list_accounting_runs, this is the rule to start with:
list_accounting_runs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every list_accounting_runs call is checked against it from then on.
Questions about list_accounting_runs
List only the caller's private Accounting-run audit metadata, newest first. Raw source text and analysis results are intentionally omitted. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
list_accounting_runs accepts 3 parameters: limit, offset, status. 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 list_accounting_runs: 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.
list_accounting_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_accounting_runs 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 list_accounting_runs. 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.
list_accounting_runs 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.
This server
Across the catalogue