Generate a YAML test spec by discovering the capabilities of an MCP server. Returns a ready-to-run spec.
AI agents call generate_spec to retrieve information from MCP Workbench MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool discovers/inspects capabilities of an MCP server and generates a YAML specification. This is a read/query operation — it retrieves information about server capabilities and produces a document. It does not modify data, execute commands, or cause destructive effects. The generated spec is an output artifact, not an action with side effects.
From the tool's definition Generate a YAML test spec by discovering the capabilities of an MCP server. Returns a ready-to-run spec.
Attacks that exploit this kind of access
Generate a YAML test spec by discovering the capabilities of an MCP server. Returns a ready-to-run spec. It is categorised as a Read tool in the MCP Workbench MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Workbench MCP Server MCP server in PolicyLayer and add a rule for generate_spec: 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 MCP Workbench MCP Server. Nothing to install.
generate_spec 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 generate_spec 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 generate_spec. 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.
generate_spec is provided by the MCP Workbench MCP Server MCP server (raeseoklee/mcp-workbench-mcp-server). 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 →