scf_rotate_webhook_secret · Scf MCP: Risk & Policy

WHAT IT DOES

What scf_rotate_webhook_secret does on Scf

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

WHY IT NEEDS A POLICY

Why scf_rotate_webhook_secret needs a policy

This tool modifies webhook security credentials by invalidating the old secret and issuing a new one. While the operation is reversible (the new secret can be rotated again), it is a sensitive mutation that affects authentication/authorization for webhook endpoints. It is not Destructive because the operation is reversible and does not permanently erase data.

From the tool's definition 'Rotate the HMAC signing secret for a webhook endpoint (write — admin role). The old secret is invalidated immediately.'

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scf_rotate_webhook_secret Rate-limited

scf_rotate_webhook_secret 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": {
    "scf_rotate_webhook_secret": {
      "limits": [
        {
          "counter": "scf_rotate_webhook_secret_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 Scf, so you can run agents against it safely.

FAQ

Questions about scf_rotate_webhook_secret

What does the scf_rotate_webhook_secret tool do? +

Rotate the HMAC signing secret for a webhook endpoint (write — admin role). The old secret is invalidated immediately. Returns the new plaintext secret exactly once. It is categorised as a Write tool in the Scf MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on scf_rotate_webhook_secret? +

Register the Scf MCP server in PolicyLayer and add a rule for scf_rotate_webhook_secret: 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 Scf. Nothing to install.

What risk level is scf_rotate_webhook_secret? +

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

Can I rate-limit scf_rotate_webhook_secret? +

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

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

scf_rotate_webhook_secret is provided by the Scf MCP server (mcp-server-scf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.