For every spec in the index that has a stored ac_hash,
AI agents call get_drift_report 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.
This tool queries an index to fetch spec drift information and generates a report. It performs passive analysis without creating, modifying, deleting, or executing external operations. It is a Read operation with minimal blast radius—worst case is stale or inaccurate drift data being returned, not destructive or financial impact.
From the tool's definition Tool description indicates it retrieves and reports on specs with stored ac_hash values. The verb 'get' and the action of generating a 'report' (analysis/output) indicate data retrieval with no modifications.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
For every spec in the index that has a stored ac_hash,. 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_drift_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 Mk Spec Master. Nothing to install.
get_drift_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 get_drift_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 get_drift_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.
get_drift_report 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 →