List all tools exposed by the connected MCP server.
AI agents call inspector_list_tools to retrieve information from Mcp Inspector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cursor | string | — | Pagination cursor from previous response (optional) |
session_id | string | Yes | Session ID returned by inspector_connect |
Parameters from the server's own tool schema.
This tool retrieves metadata about available tools from a connected MCP server. It performs a read-only query operation, returning information without creating, modifying, deleting, or executing anything. The action is informational only, making it a Read category tool with low severity since listing tools poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'inspector_list_tools' and description states it 'List[s] all tools exposed by the connected MCP server' — a pure query/retrieval operation with no side effects or modifications.
Attacks that exploit this kind of access
List all tools exposed by the connected MCP server. It is categorised as a Read tool in the Mcp Inspector MCP Server, which means it retrieves data without modifying state.
inspector_list_tools accepts 2 parameters: cursor, session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Inspector MCP server in PolicyLayer and add a rule for inspector_list_tools: 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 Inspector. Nothing to install.
inspector_list_tools 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 inspector_list_tools 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 inspector_list_tools. 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.
inspector_list_tools is provided by the Mcp Inspector MCP server (@fre4x/mcp-inspector). 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 →