Retrieve Meteor method execution traces with performance metrics. Returns traces sorted by response time with breakdown of time spent in DB, compute, HTTP, etc. IMPORTANT: Default time range is last 1 hour. If no data is returned, try a wider startTime (e.g., 24 hours or 1 week ago in milliseconds).
AI agents call get_method_traces to retrieve information from Monti APM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing performance monitoring data from Monti APM without modifying, executing operations, or affecting system state. It is purely observational/analytical in nature, making it a Read operation. The low severity reflects that misuse would only expose monitoring data without causing direct harm to the monitored application or its data.
From the tool's definition Tool description states "Retrieve Meteor method execution traces with performance metrics" and returns historical performance data with no mention of modifications, deletions, or side effects. The term "retrieve" and "get" prefix indicate data retrieval only.
Attacks that exploit this kind of access
Retrieve Meteor method execution traces with performance metrics. Returns traces sorted by response time with breakdown of time spent in DB, compute, HTTP, etc. IMPORTANT: Default time range is last 1 hour. If no data is returned, try a wider startTime (e.g., 24 hours or 1 week ago in milliseconds). It is categorised as a Read tool in the Monti APM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Monti APM MCP Server MCP server in PolicyLayer and add a rule for get_method_traces: 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 Monti APM MCP Server. Nothing to install.
get_method_traces 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_method_traces 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_method_traces. 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_method_traces is provided by the Monti APM MCP Server MCP server (quavedev/montiapm-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 →