Revoke authorization with a merchant domain
AI agents call scp_revoke_authorization to permanently remove resources in SCP Local MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking authorization is an irreversible action that terminates the OAuth 2.0 access relationship with a merchant domain. Once revoked, the authorization cannot be 'unrevoked' — a new authorization flow would need to be initiated. This is analogous to deleting access credentials, making it Destructive.
From the tool's definition Revoke authorization with a merchant domain
Attacks that exploit this kind of access
Revoke authorization with a merchant domain. It is categorised as a Destructive tool in the SCP Local MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SCP Local MCP Server MCP server in PolicyLayer and add a rule for scp_revoke_authorization: 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.
scp_revoke_authorization 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 scp_revoke_authorization 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 scp_revoke_authorization. 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.
scp_revoke_authorization 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.
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 →