AI agents call queryPinRequests to retrieve information from Pinata MCP 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 to retrieve the status of existing pin requests identified by content identifiers (CIDs). It has no side effects—it does not create, modify, delete, or trigger external operations. It is a straightforward data retrieval operation, making it a Read category tool with low severity.
From the tool's definition Tool name 'queryPinRequests' and description 'Query the status of pin by CID requests' indicate a read-only operation that retrieves status information without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access queryPinRequests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pinata MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for queryPinRequests:
{
"version": "1",
"default": "deny",
"tools": {
"queryPinRequests": {}
}
}queryPinRequests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query the status of pin by CID requests. It is categorised as a Read tool in the Pinata MCP MCP Server, which means it retrieves data without modifying state.
Register the Pinata MCP server in PolicyLayer and add a rule for queryPinRequests: 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 Pinata MCP. Nothing to install.
queryPinRequests 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 queryPinRequests 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 queryPinRequests. 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.
queryPinRequests is provided by the Pinata MCP server (pinatacloud/pinata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pinata MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
35 Pinata MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.