Get shopping intents from a merchant. Domain must be authorized first.
AI agents call scp_get_intents to retrieve information from SCP Local MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves shopping intent data from a merchant system without creating, modifying, or deleting any data. It performs a query operation on authorized customer e-commerce data. The authorization gate mitigates misuse risk.
From the tool's definition Tool name 'scp_get_intents' with description 'Get shopping intents from a merchant' — 'Get' indicates retrieval operation with no modification. The requirement that 'Domain must be authorized first' confirms this is a gated read operation.
Attacks that exploit this kind of access
Get shopping intents from a merchant. Domain must be authorized first. It is categorised as a Read tool in the SCP Local MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SCP Local MCP Server MCP server in PolicyLayer and add a rule for scp_get_intents: 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_get_intents is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scp_get_intents 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_get_intents. 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_get_intents 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 →