scp_authorize · SCP Local MCP Server MCP: Risk & Policy

WHAT IT DOES

What scp_authorize does on SCP Local MCP Server

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

WHY IT NEEDS A POLICY

Why scp_authorize needs a policy

Authorization creates a new OAuth token/session granting access to customer e-commerce data. This is a Write operation (creates an authorization record/grant) rather than Read. It is not Destructive or Financial, but misuse could expose sensitive customer data (orders, loyalty, preferences) to unauthorized merchants, giving it medium severity.

From the tool's definition Authorize access to a merchant — establishes an OAuth 2.0 authorization grant, creating a persistent access relationship

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scp_authorize Rate-limited

scp_authorize 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": {
    "scp_authorize": {
      "limits": [
        {
          "counter": "scp_authorize_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 SCP Local MCP Server, so you can run agents against it safely.

FAQ

Questions about scp_authorize

What does the scp_authorize tool do? +

BEFORE USING THIS ENSURE THE DOMAIN SUPPORTS SCP BY CALLING scp_discover FIRST. Authorize access to a merchant\. It is categorised as a Write tool in the SCP Local 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 scp_authorize? +

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

What risk level is scp_authorize? +

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

Can I rate-limit scp_authorize? +

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

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

scp_authorize is provided by the SCP Local MCP Server MCP server (shopper-context-protocol/scp-mcp-wrapper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

scp_authorize is one line of SCP Local MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →