add_secret_to_check · Pingera MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_secret_to_check does on Pingera MCP Server

AI agents use add_secret_to_check to create or update resources in Pingera MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pingera MCP Server environment.

WHY IT NEEDS A POLICY

Why add_secret_to_check needs a policy

Adding secrets to a check is a reversible write operation that modifies check configuration. While not destructive (can be removed/updated), secrets are sensitive and their addition could enable unauthorized access or expose credentials if misused. The high severity reflects the potential impact of inadvertently storing or exposing secrets through an AI agent's improper use of this tool.

From the tool's definition Tool name 'add_secret_to_check' indicates modification of check configuration by adding a secret; sibling tools like 'create_check' and 'create_check_group' confirm this server manages check resources; description is empty but name clearly implies data…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_secret_to_check Rate-limited

add_secret_to_check stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_secret_to_check": {
      "limits": [
        {
          "counter": "add_secret_to_check_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pingera MCP Server, so you can run agents against it safely.

FAQ

Questions about add_secret_to_check

What does the add_secret_to_check tool do? +

add_secret_to_check. It is categorised as a Write tool in the Pingera MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_secret_to_check? +

Register the Pingera MCP Server MCP server in PolicyLayer and add a rule for add_secret_to_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.

What risk level is add_secret_to_check? +

add_secret_to_check is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_secret_to_check? +

Yes. Add a rate_limit block to the add_secret_to_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.

How do I block add_secret_to_check completely? +

Set action: deny in the PolicyLayer policy for add_secret_to_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.

What MCP server provides add_secret_to_check? +

add_secret_to_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.