unresolve_task · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What unresolve_task does on ReliaQuest GreyMatter MCP Server

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

This tool reverses a task resolution—a write operation that modifies data state. It is not destructive (does not delete), not financial, and not execute (does not run code). The severity is medium because unresolving tasks could cause workflow disruptions or re-open resolved incidents, but the effect is reversible by resolving again.

From the tool's definition Tool name 'unresolve_task' indicates a mutation operation that modifies task state. Description confirms it is a 'mutation' (GraphQL terminology for write operations) in the Tasks domain. Variables like 'input' and 'filter' suggest parametrized state changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unresolve_task Rate-limited

unresolve_task 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": {
    "unresolve_task": {
      "limits": [
        {
          "counter": "unresolve_task_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 unresolve_task

What does the unresolve_task tool do? +

Tasks \u00b7 mutation unresolveTask. Variables: after, filter, first, order, 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 unresolve_task? +

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

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

Can I rate-limit unresolve_task? +

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

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

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