Đóng request với closure code và resolution
AI agents use close_request to create or update resources in ServiceDesk Plus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceDesk Plus MCP Server environment.
This tool modifies request state by marking it as closed, which is a significant state change in a service desk system. While the action may technically be reversible (a technician could reopen), from a functional standpoint it represents a material modification to data state. It does not delete data (thus not Destructive) nor does it execute arbitrary code (thus not Execute).
From the tool's definition The tool description states 'Đóng request với closure code và resolution' (Close request with closure code and resolution).
Attacks that exploit this kind of access
Đóng request với closure code và resolution. It is categorised as a Write tool in the ServiceDesk Plus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceDesk 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 ServiceDesk Plus MCP Server. Nothing to install.
close_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
close_request is provided by the ServiceDesk Plus MCP Server MCP server (thichcode/servicedeskplus_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →