resolve_task · ReliaQuest GreyMatter MCP Server MCP

WHAT IT DOES

What resolve_task does on ReliaQuest GreyMatter MCP Server

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

This tool creates or modifies data reversibly by updating task status and metadata. While task resolution is a state change, it is not irreversible deletion and can potentially be undone or modified in incident response systems. The severity is high because misuse could incorrectly resolve critical security incident tasks, disrupting incident response workflows.

From the tool's definition Tool description states 'Resolve a task' with input parameters taskId, closeCode, and closeNote. The action modifies task state by setting a closeCode (CANCELLED, DUPLICATE, or RESOLVED) and adding a closeNote, which are persistent changes to task records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_task Rate-limited

resolve_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": {
    "resolve_task": {
      "limits": [
        {
          "counter": "resolve_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 resolve_task

What does the resolve_task tool do? +

Resolve a task. input: ResolveTaskInput { taskId, closeCode (CANCELLED, DUPLICATE, or RESOLVED), closeNote }. 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 resolve_task? +

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

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

Can I rate-limit resolve_task? +

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

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

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