Connect to an MCP server and inspect its capabilities, version, and supported features.
AI agents call inspect_server 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.
This tool retrieves metadata about MCP servers (capabilities, version, features) without modifying state, executing code, or causing side effects. It is a diagnostic/discovery operation typical of Read category tools. Severity is low because inspection has minimal blast radius—no data is modified or executed.
From the tool's definition Tool description states 'inspect its capabilities, version, and supported features' — pure query operations with no modification or execution. The verb 'inspect' and 'connect' indicate information retrieval only.
Attacks that exploit this kind of access
Connect to an MCP server and inspect its capabilities, version, and supported features. 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 inspect_server: 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.
inspect_server 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 inspect_server 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 inspect_server. 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.
inspect_server 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 →