Get full profile for a customer id (e.g. CUST-1001).
AI agents call get_customer to retrieve information from Acme Operations Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves customer profile information based on a provided customer ID. It performs a read-only lookup operation with no side effects, no data modification, no code execution, and no financial transactions. The confidentiality sensitivity of customer data is mitigated by the fact that access control is presumed to be enforced at the server level rather than by the tool itself.
From the tool's definition Tool name 'get_customer' and description 'Get full profile for a customer id' indicate a retrieval operation that queries customer data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get full profile for a customer id (e.g. CUST-1001). It is categorised as a Read tool in the Acme Operations Assistant MCP Server, which means it retrieves data without modifying state.
Register the Acme Operations Assistant 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 Acme Operations Assistant. 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 Acme Operations Assistant MCP server (yesidevelop/simple-mcp-server). 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 →