User \u00b7 mutation createUser. Variables: after, filter, first, order, after1, filter1, first1, order1, after2, filter2, first2, order2, input. Example variables: {\
AI agents use create_user to create or update resources in ReliaQuest GreyMatter MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReliaQuest GreyMatter MCP Server environment.
The tool creates a new user account, which is a reversible Write operation that modifies the user database. Severity is high because creating unauthorized user accounts could grant unintended access to the GreyMatter platform and compromise incident response workflows. This is not Destructive (user accounts can be deleted), not Execute (no arbitrary code/command execution), and not Financial (no money movement).
From the tool's definition Tool name 'create_user' and description indicating a GraphQL mutation for user creation. The presence of 'input' variables confirms it modifies data by creating a new user record.
Attacks that exploit this kind of access
User \u00b7 mutation createUser. Variables: after, filter, first, order, after1, filter1, first1, order1, after2, filter2, first2, order2, input. Example variables: {\. It is categorised as a Write tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for create_user: 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.
create_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_user 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 create_user. 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.
create_user 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 →