get_accounting_run
Get one private Accounting run owned by the caller, including its deterministic estimates, disclaimer, engine revision, and audit timestamps. Source input stays omitted unless include_input=true is explicitly requested.
This record as markdown: /tools/com-meta-council-decision-intelligence/get-accounting-run.md
What get_accounting_run does on Meta Council
AI agents call get_accounting_run 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 |
|---|---|---|---|
run_id | string | Yes | |
include_input | boolean | — | Also return the caller's decrypted source text; use sparingly. |
Parameters from the server's own tool schema.
Why get_accounting_run is rated Low
This tool retrieves accounting run data that the caller owns. It performs no side effects, does not execute external operations, does not modify or delete data, and does not involve financial transactions. The optional 'include_input' parameter controls verbosity but does not change the fundamental read-only nature.
From the tool's definition Tool description explicitly states 'Get one private Accounting run' — a retrieval operation with no modification, creation, or deletion.
Attacks that exploit this kind of access
The rule that runs get_accounting_run 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 get_accounting_run, this is the rule to start with:
get_accounting_run 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 get_accounting_run call is checked against it from then on.
Questions about get_accounting_run
Get one private Accounting run owned by the caller, including its deterministic estimates, disclaimer, engine revision, and audit timestamps. Source input stays omitted unless include_input=true is explicitly requested. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_accounting_run accepts 2 parameters: run_id, include_input. Required: run_id. 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 get_accounting_run: 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.
get_accounting_run 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 get_accounting_run 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 get_accounting_run. 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.
get_accounting_run 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