update_check_secrets · Pingera MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_check_secrets does on Pingera MCP Server

AI agents use update_check_secrets 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 update_check_secrets needs a policy

This tool creates or modifies secrets associated with monitoring checks, which are sensitive credentials. While reversible (Write category, not Destructive), misuse could expose or corrupt authentication credentials used by monitoring probes. Severity is high due to the sensitive nature of secrets, though confidence is moderate because the description is missing.

From the tool's definition Tool name 'update_check_secrets' indicates modification of secrets stored in monitoring checks. The verb 'update' suggests a Write operation. Context from sibling tool 'add_secret_to_check' confirms this server manages secrets.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_check_secrets Rate-limited

update_check_secrets 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": {
    "update_check_secrets": {
      "limits": [
        {
          "counter": "update_check_secrets_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 update_check_secrets

What does the update_check_secrets tool do? +

update_check_secrets. 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 update_check_secrets? +

Register the Pingera MCP Server MCP server in PolicyLayer and add a rule for update_check_secrets: 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 update_check_secrets? +

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

Can I rate-limit update_check_secrets? +

Yes. Add a rate_limit block to the update_check_secrets 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 update_check_secrets completely? +

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

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