Get details of a specific request by ID
AI agents call get_request to retrieve information from Service Desk 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 information about an existing service desk request. It performs a read-only query that returns data without creating, modifying, deleting, or executing any actions. While the data retrieved might be sensitive (service desk requests could contain customer information), the tool itself has no capability to cause adverse effects.
From the tool's definition Tool description states 'Get details of a specific request by ID' - a retrieval operation with no modification or side effects. The verb 'Get' and the context of retrieving a specific request by identifier indicate a straightforward query operation.
Attacks that exploit this kind of access
Get details of a specific request by ID. It is categorised as a Read tool in the Service Desk Plus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Service Desk Plus MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_request 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 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. 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 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.
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 →