Get ticket fields from Freshservice.
AI agents call get_ticket_fields 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.
This tool retrieves metadata about ticket fields available in Freshservice. It performs no write operations, does not execute code or commands, does not delete data, and has no financial impact. The primary risk is information disclosure, which is minimal for field schema metadata.
From the tool's definition Tool name 'get_ticket_fields' and description 'Get ticket fields from Freshservice' indicate a retrieval operation with no side effects. The verb 'Get' and lack of any modification, deletion, or execution semantics confirm this is a data query operation.
Attacks that exploit this kind of access
Get ticket fields from Freshservice. 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_ticket_fields: 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_ticket_fields 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_ticket_fields 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_ticket_fields. 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_ticket_fields 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 →