enable_user · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What enable_user does on ReliaQuest GreyMatter MCP Server

AI agents use enable_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.

WHY IT NEEDS A POLICY

Why enable_user needs a policy

Enabling a user is a reversible modification to user status/permissions in an access control system. It creates or modifies account state without permanently destroying data. This is less severe than Destructive (which would be permanent deletion) but more severe than Read operations. It could allow unauthorized access if misused by an AI agent, but remains reversible through a disable_user operation.

From the tool's definition Tool name 'enable_user' and description indicating a 'mutation enableUser' indicates a state-changing operation that modifies user data/status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enable_user Rate-limited

enable_user stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "enable_user": {
      "limits": [
        {
          "counter": "enable_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ReliaQuest GreyMatter MCP Server, so you can run agents against it safely.

FAQ

Questions about enable_user

What does the enable_user tool do? +

User \u00b7 mutation enableUser. Variables: after, filter, first, order, after1, filter1, first1, order1, after2, filter2, first2, order2, user. 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.

How do I enforce a policy on enable_user? +

Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for enable_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.

What risk level is enable_user? +

enable_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit enable_user? +

Yes. Add a rate_limit block to the enable_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.

How do I block enable_user completely? +

Set action: deny in the PolicyLayer policy for enable_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.

What MCP server provides enable_user? +

enable_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.