AI agents call read_resource to retrieve information from Vaiz MCP 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 data (reading resource content) with no side effects. It is a straightforward read operation consistent with the 'Read' category definition. The low severity reflects minimal blast radius—retrieving existing data poses no risk of unintended modifications, deletions, or external operations.
From the tool's definition Tool name explicitly states 'read_resource' and description confirms it 'Read[s] content of a specific MCP resource by name'. No modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
Read content of a specific MCP resource by name. For knowledge base articles, use. It is categorised as a Read tool in the Vaiz MCP MCP Server, which means it retrieves data without modifying state.
Register the Vaiz MCP server in PolicyLayer and add a rule for 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 Vaiz MCP. Nothing to install.
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 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 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.
read_resource is provided by the Vaiz MCP server (vaizcom/vaiz-mcp). 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 →