Emergency stop! Sends Reset All Controllers, All Sound Off, and All Notes Off to FM8. Use this to immediately silence all sounds.
AI agents invoke fm8_panic to trigger actions in FM8 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.
This tool triggers external operations on FM8 synthesizer hardware/software via MIDI messages (reset, sound off, notes off). It executes commands with immediate real-time effects on an external system. While it's a safety/emergency stop function, it actively sends multiple MIDI control messages that affect the synthesizer's state.
From the tool's definition Sends Reset All Controllers, All Sound Off, and All Notes Off to FM8. Use this to immediately silence all sounds.
Attacks that exploit this kind of access
Emergency stop! Sends Reset All Controllers, All Sound Off, and All Notes Off to FM8. Use this to immediately silence all sounds. It is categorised as a Execute tool in the FM8 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FM8 MCP Server MCP server in PolicyLayer and add a rule for fm8_panic: 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 FM8 MCP Server. Nothing to install.
fm8_panic 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 fm8_panic 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 fm8_panic. 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.
fm8_panic is provided by the FM8 MCP Server MCP server (thesigma1receptor/fm8mcp). 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 →