Customer \u00b7 query customer. Variables: after, first, after1, first1. Example variables: {\
AI agents call customer to retrieve information from ReliaQuest GreyMatter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries customer information from the GreyMatter platform. It retrieves data with no side effects, falling squarely into the Read category. The pagination variables confirm this is a data retrieval operation. Severity is low as querying customer data alone poses minimal risk compared to modification or destruction; however, the actual severity would depend on what customer data is exposed and to whom.
From the tool's definition Tool name 'customer' with description 'query customer' indicates a retrieval operation. The variables (after, first, after1, first1) suggest pagination parameters typical of GraphQL queries used to fetch customer data without modification.
Attacks that exploit this kind of access
Customer \u00b7 query customer. Variables: after, first, after1, first1. Example variables: {\. It is categorised as a Read tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for 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 ReliaQuest GreyMatter MCP Server. Nothing to install.
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 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 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.
customer is provided by the ReliaQuest GreyMatter MCP Server MCP server (space-c0wboy/reliaquest-greymatter-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 →