Check if the local data file was successfully loaded.
AI agents call system_status 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.
The tool performs a diagnostic query to verify the state of a loaded data file. This is purely informational with no side effects, no code execution, no data modification, and no destructive capability. It aligns with the Read category as a retrieval operation. Severity is low because misuse would only reveal status information with minimal blast radius.
From the tool's definition Tool name and description indicate a status check operation: 'Check if the local data file was successfully loaded.' This is a read-only query that retrieves system state information without modifying, executing, or destroying anything.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Check if the local data file was successfully loaded. 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 system_status: 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.
system_status 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 system_status 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 system_status. 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.
system_status 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 →