outstanding_report
AI agents call outstanding_report to retrieve information from ERP-File MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Outstanding reports are typically read-only queries that retrieve financial/sales data without modifying state. No evidence of data modification, deletion, or external action execution. The empty description prevents higher confidence, but the semantic context (report suffix, ERP query pattern, non-destructive siblings) strongly suggests a Read operation with low blast radius.
From the tool's definition Tool name 'outstanding_report' combined with sibling tools 'sales_report', 'dead_client_report', and 'unbilled_report' pattern suggests report generation/querying. The server description emphasizes 'querying ERP data' as a primary capability.
Attacks that exploit this kind of access
outstanding_report. It is categorised as a Read tool in the ERP-File MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ERP-File MCP Server MCP server in PolicyLayer and add a rule for outstanding_report: 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 ERP-File MCP Server. Nothing to install.
outstanding_report 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 outstanding_report 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 outstanding_report. 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.
outstanding_report is provided by the ERP-File MCP Server MCP server (sharpjsdev/mcp-server). 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 →