close_request · Service Desk Plus MCP Server MCP

WHAT IT DOES

What close_request does on Service Desk Plus MCP Server

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

WHY IT NEEDS A POLICY

Why close_request needs a policy

Closing a request modifies the state of a service desk entity (marking it as resolved/closed) but does not permanently delete data. This is reversible—requests can be reopened or status changed. While impactful (high severity due to potential workflow disruption if misused), it falls under Write rather than Destructive since the underlying data persists and the action can be undone.

From the tool's definition Tool name 'close_request' and description 'Close a request with resolution details' indicates modification of request state to a closed/resolved status, which is a reversible write operation on service desk data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_request Rate-limited

close_request 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_request": {
      "limits": [
        {
          "counter": "close_request_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 Service Desk Plus MCP Server, so you can run agents against it safely.

FAQ

Questions about close_request

What does the close_request tool do? +

Close a request with resolution details. It is categorised as a Write tool in the Service Desk Plus 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_request? +

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

What risk level is close_request? +

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

Can I rate-limit close_request? +

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

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

close_request is provided by the Service Desk Plus MCP Server MCP server (pttg-it/sdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.