AI agents invoke perform_magic_operation to trigger actions in CyberChef API MCP Server. 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.
CyberChef's Magic operation executes a series of transformations determined by the input data. This constitutes code execution (though constrained to CyberChef's recipe engine). The severity is medium rather than high because CyberChef operations are typically data-transformation-only with limited side effects, but the automatic nature and breadth of possible transformations warrant caution.
From the tool's definition Tool name 'perform_magic_operation' on a CyberChef API server suggests execution of arbitrary data transformations. The description is empty, which limits certainty.
Documented attack patterns abuse exactly the kind of access perform_magic_operation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CyberChef API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for perform_magic_operation:
{
"version": "1",
"default": "deny",
"tools": {
"perform_magic_operation": {
"limits": [
{
"counter": "perform_magic_operation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}perform_magic_operation 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.
Free to start. No card required.
perform_magic_operation. It is categorised as a Execute tool in the CyberChef API MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CyberChef API MCP Server MCP server in PolicyLayer and add a rule for perform_magic_operation: 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 CyberChef API MCP Server. Nothing to install.
perform_magic_operation 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 perform_magic_operation 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 perform_magic_operation. 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.
perform_magic_operation is provided by the CyberChef API MCP Server MCP server (slouchd/cyberchef-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 CyberChef API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 CyberChef API MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.