Lấy lịch sử/timeline của request
AI agents call get_request_history to retrieve information from ServiceDesk Plus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about a request (ticket/ticket timeline). It performs a query operation that does not modify, delete, or execute any actions—it simply fetches existing data. This is a classic Read operation with minimal blast radius if misused by an AI agent, as it only exposes historical audit/timeline data already associated with the request.
From the tool's definition Tool name 'get_request_history' and description 'Lấy lịch sử/timeline của request' (retrieve history/timeline of request) indicate data retrieval without side effects.
Attacks that exploit this kind of access
Lấy lịch sử/timeline của request. It is categorised as a Read tool in the ServiceDesk Plus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceDesk Plus MCP Server MCP server in PolicyLayer and add a rule for get_request_history: 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.
get_request_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_request_history 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 get_request_history. 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.
get_request_history 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 →