Decrypt PGP-encrypted data or files using a private key stored in Pincer
AI agents invoke gpg_decrypt to trigger actions in Pincer. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Decryption is an active operation that uses a stored private key to process encrypted data. It is not a simple read (it transforms ciphertext into plaintext using sensitive key material), and misuse could expose confidential data or allow an agent to decrypt messages/files it shouldn't access. The involvement of private key material raises the blast radius significantly.
From the tool's definition Decrypt PGP-encrypted data or files using a private key stored in Pincer
Documented attack patterns abuse exactly the kind of access gpg_decrypt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pincer, and nothing reaches the server without passing your rules. This is the rule we recommend for gpg_decrypt:
{
"version": "1",
"default": "deny",
"tools": {
"gpg_decrypt": {
"limits": [
{
"counter": "gpg_decrypt_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}gpg_decrypt stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Decrypt PGP-encrypted data or files using a private key stored in Pincer. It is categorised as a Execute tool in the Pincer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pincer MCP server in PolicyLayer and add a rule for gpg_decrypt: 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 Pincer. Nothing to install.
gpg_decrypt is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gpg_decrypt 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 gpg_decrypt. 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.
gpg_decrypt is provided by the Pincer MCP server (VouchlyAI/Pincer-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pincer, 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.
12 Pincer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.