Enumerate specs from the active source. For markdown_local this
AI agents call list_specs 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 retrieves or queries specification metadata from a configured source (markdown_local, Linear, JIRA, GitHub Issues, Notion, or Figma) without creating, modifying, deleting, or executing operations. It presents no financial risk, cannot destructively alter data, and does not trigger external side effects. The blast radius of misuse is limited to information disclosure of existing specs.
From the tool's definition Tool name 'list_specs' with description 'Enumerate specs from the active source' indicates a retrieval operation with no modification or execution of external operations.
Attacks that exploit this kind of access
Enumerate specs from the active source. For markdown_local this. 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 list_specs: 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.
list_specs 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 list_specs 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 list_specs. 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.
list_specs 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 →