remove_child_from_case

WHAT IT DOES

What remove_child_from_case does on ReliaQuest GreyMatter MCP Server

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

This is a GraphQL mutation that removes a child association from a case. While 'remove' sounds destructive, removing a relationship/link between cases is typically a reversible write operation (the child case still exists, only the association is removed). Severity is medium given it modifies case structure in an incident response platform, which could affect investigation workflows.

From the tool's definition mutation removeChildFromCase — removes a child relationship from a case, which is a modification of case structure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_child_from_case Rate-limited

remove_child_from_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": {
    "remove_child_from_case": {
      "limits": [
        {
          "counter": "remove_child_from_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 remove_child_from_case

What does the remove_child_from_case tool do? +

Cases \u00b7 mutation removeChildFromCase. 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 remove_child_from_case? +

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

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

Can I rate-limit remove_child_from_case? +

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

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

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