Get recent ingestion run history. Shows run_id, carrier, mode, counts,
AI agents call run_history to retrieve information from Carrier Accounting MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only fetches and displays past run history data (run IDs, carriers, modes, counts). It performs no modifications, deletions, or executions. Misuse potential is minimal as it only exposes operational metadata.
From the tool's definition 'Get recent ingestion run history. Shows run_id, carrier, mode, counts' — purely retrieves historical records with no side effects
Attacks that exploit this kind of access
Get recent ingestion run history. Shows run_id, carrier, mode, counts,. It is categorised as a Read tool in the Carrier Accounting MCP MCP Server, which means it retrieves data without modifying state.
Register the Carrier Accounting MCP server in PolicyLayer and add a rule for run_history: 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 Carrier Accounting MCP. Nothing to install.
run_history 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 run_history 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 run_history. 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.
run_history is provided by the Carrier Accounting MCP server (pramodmisra/carrier-accounting-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →