Read the contents of a resource by URI from the connected MCP server.
AI agents call inspector_read_resource 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 |
|---|---|---|---|
uri | string | Yes | Resource URI to read |
session_id | string | Yes | Session ID returned by inspector_connect |
Parameters from the server's own tool schema.
This tool retrieves data (resource contents) from an MCP server without modifying or deleting anything. It is a read operation. Severity is medium rather than low because the resource contents could be sensitive (credentials, API keys, config files, etc.) depending on what resources are exposed by the connected MCP server, creating potential information disclosure risk if an agent reads unauthorized resources.
From the tool's definition Tool name and description: 'Read the contents of a resource by URI' — the verb 'read' and 'contents' indicate data retrieval with no modification. The function retrieves resource data from a connected MCP server.
Risk signalsAccepts URL/endpoint input (uri)
Attacks that exploit this kind of access
Read the contents of a resource by URI from 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_read_resource accepts 2 parameters: uri, session_id. Required: uri, 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_read_resource: 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_read_resource 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_read_resource 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_read_resource. 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_read_resource 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 →