remove_secret_from_check
AI agents call remove_secret_from_check to permanently remove resources in Pingera MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name strongly suggests removing a secret (such as an API key or credential) from a monitoring check. Removal operations are typically irreversible (the association is deleted), making this Destructive. The severity is high because removing secrets from checks could break monitoring functionality or expose security misconfigurations.
From the tool's definition Tool name 'remove_secret_from_check' implies irreversible removal of a secret (credential/token) from a check configuration.
Attacks that exploit this kind of access
remove_secret_from_check. It is categorised as a Destructive tool in the Pingera MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pingera MCP Server MCP server in PolicyLayer and add a rule for remove_secret_from_check: 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 Pingera MCP Server. Nothing to install.
remove_secret_from_check 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 remove_secret_from_check 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 remove_secret_from_check. 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.
remove_secret_from_check is provided by the Pingera MCP Server MCP server (pingera/pingera-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 →