Get a specific customer by ID
AI agents call inbox_get_customer to retrieve information from MCP Help Scout without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves customer information by ID from the Help Scout Inbox API. It is a straightforward read operation that queries data without side effects, aligning with the Read category. The severity is low because retrieving customer metadata poses minimal risk even if accessed by an AI agent without authorization, though data sensitivity should be considered in a broader privacy context.
From the tool's definition Tool name 'inbox_get_customer' and description 'Get a specific customer by ID' indicate retrieval of existing customer data with no modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get a specific customer by ID. It is categorised as a Read tool in the MCP Help Scout MCP Server, which means it retrieves data without modifying state.
Register the MCP Help Scout MCP server in PolicyLayer and add a rule for inbox_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 MCP Help Scout. Nothing to install.
inbox_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 inbox_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 inbox_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.
inbox_get_customer is provided by the MCP Help Scout MCP server (solveitsimply/mcp-helpscout). 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 →