get_customer
Get detailed information about a single customer by their ID.
This record as markdown: /tools/abbottdevelopments-shopmonkey-mcp-server/get-customer.md
What get_customer does on Shopmonkey MCP Server
AI agents call get_customer to retrieve information from Shopmonkey MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_customer is rated Low
This tool only retrieves and queries existing customer data. It does not create, modify, delete, or execute any operations. It is a straightforward read operation that returns information about a single customer record, posing no destructive or operational risk.
From the tool's definition Tool description states 'Get detailed information about a single customer by their ID' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_customer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Shopmonkey MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_customer, this is the rule to start with:
get_customer is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Shopmonkey MCP Server, apply this rule, and every get_customer call is checked against it from then on.
Questions about get_customer
Get detailed information about a single customer by their ID. It is categorised as a Read tool in the Shopmonkey MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shopmonkey MCP Server MCP server in PolicyLayer and add a rule for get_customer: 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 Shopmonkey MCP Server. Nothing to install.
get_customer 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 get_customer 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 get_customer. 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.
get_customer is provided by the Shopmonkey MCP Server MCP server (abbottdevelopments/shopmonkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Shopmonkey MCP Server, and thousands of servers like it.
This server
Across the catalogue