Update an existing knowledge base article
AI agents use update_solution_article to create or update resources in Freshservice MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshservice MCP Server environment.
This tool modifies (updates) existing knowledge base articles without permanently deleting them. Updates are typically reversible through version history or subsequent edits. It falls under Write rather than Destructive because the action does not irreversibly delete or overwrite data.
From the tool's definition Tool name 'update_solution_article' and description 'Update an existing knowledge base article' indicate modification of existing data in a reversible manner.
Attacks that exploit this kind of access
Update an existing knowledge base article. It is categorised as a Write tool in the Freshservice MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for update_solution_article: 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.
update_solution_article is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_solution_article 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 update_solution_article. 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.
update_solution_article is provided by the Freshservice MCP Server MCP server (tannertm0/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 →