View a specific change approval.
AI agents call view_change_approval 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 or queries information about a specific change approval in the Freshservice platform. It performs a read-only operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius is minimal—viewing approval information cannot cause harm or unintended consequences.
From the tool's definition Tool name 'view_change_approval' and description 'View a specific change approval' indicate retrieval of existing approval data with no modification or execution.
Attacks that exploit this kind of access
View a specific change approval. 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 view_change_approval: 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.
view_change_approval 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 view_change_approval 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 view_change_approval. 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.
view_change_approval 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 →