AI agents call get_public_resource to retrieve information from Yadisk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation on publicly-accessible resources, returning metadata or information without side effects. It does not modify data, execute commands, delete anything, or involve financial transactions. The public nature of the resources limits the sensitivity of the information retrieved.
From the tool's definition Tool retrieves information about public resources using identifiers (public key or URL). The description uses "Get information" which indicates data retrieval with no modification or deletion. The tool is reading metadata about already-published resources.
Attacks that exploit this kind of access
Get information about a public resource by its public key or URL. It is categorised as a Read tool in the Yadisk MCP Server, which means it retrieves data without modifying state.
Register the Yadisk MCP server in PolicyLayer and add a rule for get_public_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 Yadisk. Nothing to install.
get_public_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 get_public_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 get_public_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.
get_public_resource is provided by the Yadisk MCP server (patr56/yadisk-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 →