Fetch requested items for a specific ticket if the ticket is a service request.
AI agents call get_requested_items to retrieve information from Freshservice MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries data about requested items associated with a service request ticket, with no capability to modify, delete, or execute operations. This is a standard read operation typical of IT service management platforms. Severity is low because exposure of service request item data generally poses minimal risk in a business context.
From the tool's definition 'Fetch requested items' indicates data retrieval; 'if the ticket is a service request' shows it queries information without modification or side effects.
Attacks that exploit this kind of access
Fetch requested items for a specific ticket if the ticket is a service request. It is categorised as a Read tool in the Freshservice MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for get_requested_items: 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 Freshservice MCP Server. Nothing to install.
get_requested_items 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_requested_items 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_requested_items. 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_requested_items is provided by the Freshservice MCP Server MCP server (leemangold/freshservice_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 →