accept_incident_solution · InvGate Service Desk MCP

WHAT IT DOES

What accept_incident_solution does on InvGate Service Desk

AI agents use accept_incident_solution to create or update resources in InvGate Service Desk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your InvGate Service Desk environment.

WHY IT NEEDS A POLICY

Why accept_incident_solution needs a policy

This tool modifies the state of an incident/request by accepting its solution and adding a rating. This is a reversible state change (writing acceptance status and rating) rather than deletion, code execution, or financial action. Misuse could prematurely close legitimate incidents, but the blast radius is limited to individual tickets.

From the tool's definition Accept the solution of a request, with a rating

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

accept_incident_solution Rate-limited

accept_incident_solution 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": {
    "accept_incident_solution": {
      "limits": [
        {
          "counter": "accept_incident_solution_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 InvGate Service Desk, so you can run agents against it safely.

FAQ

Questions about accept_incident_solution

What does the accept_incident_solution tool do? +

Accept the solution of a request, with a rating. It is categorised as a Write tool in the InvGate Service Desk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on accept_incident_solution? +

Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for accept_incident_solution: 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 InvGate Service Desk. Nothing to install.

What risk level is accept_incident_solution? +

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

Can I rate-limit accept_incident_solution? +

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

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

accept_incident_solution is provided by the InvGate Service Desk MCP server (oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.