calculate_mps_metrics
AI agents call calculate_mps_metrics to retrieve information from M/M/1 and M/M/c Queue Simulation Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to calculate and return theoretical metrics for queuing analysis without modifying, deleting, or executing external operations. The pattern matches Read category (retrieves/queries computed data). Confidence is moderate (0.75) due to empty description, but the naming and server context strongly indicate a calculation/analysis utility.
From the tool's definition Tool name 'calculate_mps_metrics' and context indicating it performs 'theoretical metric calculation' for queuing systems; no description provided but sibling tool 'calculate_metrics' suggests Read operations.
Attacks that exploit this kind of access
calculate_mps_metrics. It is categorised as a Read tool in the M/M/1 and M/M/c Queue Simulation Server MCP Server, which means it retrieves data without modifying state.
Register the M/M/1 and M/M/c Queue Simulation Server MCP server in PolicyLayer and add a rule for calculate_mps_metrics: 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 M/M/1 and M/M/c Queue Simulation Server. Nothing to install.
calculate_mps_metrics 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 calculate_mps_metrics 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 calculate_mps_metrics. 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.
calculate_mps_metrics is provided by the M/M/1 and M/M/c Queue Simulation Server MCP server (kiyoung8/simulation_by_simpy_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 →