Get the total amount spent by a customer.
AI agents call get_total_spent_by_customer to retrieve information from MCP GraphQL Sales Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregated financial information (total spending) about a customer from the database. It performs no mutations, deletions, or external side effects—it only fetches and calculates data. While the result involves financial amounts, the tool itself does not move money, create obligations, or execute transactions; it merely reads historical transaction summaries.
From the tool's definition Tool name 'get_total_spent_by_customer' and description 'Get the total amount spent by a customer' indicate a retrieval operation that queries sales data without modifying or deleting anything.
Attacks that exploit this kind of access
Get the total amount spent by a customer. It is categorised as a Read tool in the MCP GraphQL Sales Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GraphQL Sales Server MCP server in PolicyLayer and add a rule for get_total_spent_by_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 GraphQL Sales Server. Nothing to install.
get_total_spent_by_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_total_spent_by_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_total_spent_by_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_total_spent_by_customer is provided by the MCP GraphQL Sales Server MCP server (jambelg/mcp-graphql-claude). 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 →