Aggregate the tool-usage log written by this server.
AI agents call get_telemetry to retrieve information from Mk Spec Master without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'aggregate' combined with 'tool-usage log' indicates a retrieval and summarization operation over existing data. No side effects, no data modification, no code execution, and no destructive actions are implied. This is a straightforward Read operation with minimal risk even if misused—at worst, an agent could retrieve internal usage statistics about the server itself, which represents low sensitivity data.
From the tool's definition Tool name and description: 'Aggregate the tool-usage log written by this server.' This tool reads and aggregates existing telemetry/usage log data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Aggregate the tool-usage log written by this server. It is categorised as a Read tool in the Mk Spec Master MCP Server, which means it retrieves data without modifying state.
Register the Mk Spec Master MCP server in PolicyLayer and add a rule for get_telemetry: 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 Mk Spec Master. Nothing to install.
get_telemetry 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_telemetry 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_telemetry. 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_telemetry is provided by the Mk Spec Master MCP server (kao273183/mk-spec-master). 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 →