Access customer information and service history for support tickets
AI agents call customer-service-portal to retrieve information from IMCP - Insecure Model Context Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves customer data and support ticket history for support purposes. While it performs reads only (no write, execute, or destructive operations), the severity is medium rather than low because customer information is sensitive PII/business data; unauthorized or incorrect use by an AI agent could expose private customer details, create support incidents, or enable data exfiltration.
From the tool's definition Tool description states it 'Access customer information and service history' - these are retrieval operations with no modification capability mentioned. The term 'Access' and 'information...history' indicate read-only queries.
Attacks that exploit this kind of access
Access customer information and service history for support tickets. It is categorised as a Read tool in the IMCP - Insecure Model Context Protocol MCP Server, which means it retrieves data without modifying state.
Register the IMCP - Insecure Model Context Protocol MCP server in PolicyLayer and add a rule for customer-service-portal: 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 IMCP - Insecure Model Context Protocol. Nothing to install.
customer-service-portal 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 customer-service-portal 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 customer-service-portal. 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.
customer-service-portal is provided by the IMCP - Insecure Model Context Protocol MCP server (nav33n25/imcp). 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 →