View a specific task for a change.
AI agents call view_change_task 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 change task without modifying, executing code, deleting, or moving money. It has no side effects and falls squarely into the Read category. Severity is low because viewing task data carries minimal risk if accessed by an unauthorized agent—it is informational only.
From the tool's definition Tool name 'view_change_task' and description 'View a specific task for a change' indicate a read-only retrieval operation. The verb 'view' and the absence of any modification, execution, or destructive language confirm this is a query operation.
Attacks that exploit this kind of access
View a specific task for a change. 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_task: 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_task 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_task 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_task. 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_task 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 →