reply_to_requester · Service Desk Plus MCP Server MCP

WHAT IT DOES

What reply_to_requester does on Service Desk Plus MCP Server

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

This tool creates and sends new data (an email message) that persists in the ticket system. While email sending cannot be easily undone once delivered, it is not classified as Destructive because the original ticket and requester data remain intact. It is Write category because it adds new content to the ticket conversation.

From the tool's definition Tool description states 'Send an email reply to the requester that appears in the ticket conversation' - this creates new communication data in the ticket system and sends outbound email, modifying the ticket's conversation history irreversibly from a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reply_to_requester Rate-limited

reply_to_requester 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": {
    "reply_to_requester": {
      "limits": [
        {
          "counter": "reply_to_requester_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 reply_to_requester

What does the reply_to_requester tool do? +

Send an email reply to the requester that appears in the ticket conversation. 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 reply_to_requester? +

Register the Service Desk Plus MCP Server MCP server in PolicyLayer and add a rule for reply_to_requester: 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 reply_to_requester? +

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

Can I rate-limit reply_to_requester? +

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

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

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