character_performance
Animate a character with facial expressions and body movements from a reference performance video (Act-Two).
This record as markdown: /tools/freshdesk/character-performance.md
What character_performance does on Freshdesk
AI agents invoke character_performance to trigger actions in Freshdesk. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why character_performance is rated High
This tool executes an animation/rendering operation on external systems (Act-Two service). While not destructive or financial, it runs code/operations that transform inputs into side effects (rendered animations).
From the tool's definition Tool description states it 'Animate a character with facial expressions and body movements from a reference performance video', which triggers external animation operations whose effects depend on the input video reference and animation parameters.
Attacks that exploit this kind of access
The rule that runs character_performance 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 character_performance, this is the rule to start with:
character_performance stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 character_performance call is checked against it from then on.
Questions about character_performance
Animate a character with facial expressions and body movements from a reference performance video (Act-Two). It is categorised as a Execute tool in the Freshdesk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Freshdesk MCP server in PolicyLayer and add a rule for character_performance: 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.
character_performance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the character_performance 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 character_performance. 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.
character_performance 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.
Across the catalogue