AI agents call deleteSignature to permanently remove resources in Pinata MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion of data (a signature). Although the blast radius is somewhat contained to signature metadata rather than the content itself, the action cannot be undone and removes authentication/verification information. This qualifies as Destructive rather than Write because removal of signatures is not easily reversible and alters the security properties of the content.
From the tool's definition "Remove a signature from a CID" — this operation irreversibly deletes a signature associated with content, preventing its recovery without re-signing the CID.
Documented attack patterns abuse exactly the kind of access deleteSignature 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 deleteSignature:
{
"version": "1",
"default": "deny",
"hide": [
"deleteSignature"
]
}deleteSignature disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a signature from a CID. It is categorised as a Destructive tool in the Pinata MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pinata MCP server in PolicyLayer and add a rule for deleteSignature: 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.
deleteSignature is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteSignature 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 deleteSignature. 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.
deleteSignature 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.