publish_agent
Publish a specific agent version, making it the active/live version. WHEN TO USE: - After updating an agent
This record as markdown: /tools/freshdesk/publish-agent.md
What publish_agent does on Freshdesk
AI agents use publish_agent to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.
Why publish_agent is rated Medium
This tool changes the active agent version in a production environment. While not irreversible (a new version can be published to replace it), it is a consequential write operation that immediately affects live systems and users. It modifies state persistently and could impact service availability or behavior if the wrong version is published.
From the tool's definition 'Publish a specific agent version, making it the active/live version' — this modifies the live/active state of an agent, changing what is currently running in production.
Attacks that exploit this kind of access
The rule that runs publish_agent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For publish_agent, this is the rule to start with:
publish_agent stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every publish_agent call is checked against it from then on.
Questions about publish_agent
Publish a specific agent version, making it the active/live version. WHEN TO USE: - After updating an agent. It is categorised as a Write tool in the Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshdesk MCP server in PolicyLayer and add a rule for publish_agent: 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 Freshdesk. Nothing to install.
publish_agent 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 publish_agent 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 publish_agent. 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.
publish_agent is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue