close_case · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What close_case does on ReliaQuest GreyMatter MCP Server

AI agents use close_case 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 close_case needs a policy

This tool modifies case status by closing a case—a reversible write operation. While it changes data state, closing a case is typically reversible (cases can be reopened in incident response systems). This does not constitute a destructive delete/purge operation, nor does it execute arbitrary code or affect finances.

From the tool's definition The tool is named 'close_case' and explicitly described as a 'mutation' operation that modifies case state. GraphQL mutations are write operations that alter server-side data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_case Rate-limited

close_case 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": {
    "close_case": {
      "limits": [
        {
          "counter": "close_case_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 close_case

What does the close_case tool do? +

Cases \u00b7 mutation closeCase. Variables: 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.

How do I enforce a policy on close_case? +

Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for close_case: 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 close_case? +

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

Can I rate-limit close_case? +

Yes. Add a rate_limit block to the close_case 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 close_case completely? +

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

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