Apply gravitational funnel pull toward a target pitch.
AI agents invoke constraint_funnel to trigger actions in Constraint. 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 executes a constraint-based audio transformation operation whose effects depend on supplied arguments (target pitch, intensity/gravity parameters). While not destructive or financial, it triggers external computation that modifies audio state in a manner that cannot be undone without re-rendering.
From the tool's definition Tool description states 'Apply gravitational funnel pull toward a target pitch' which indicates execution of audio processing algorithms that transform or manipulate pitch in real-time based on parameters.
Attacks that exploit this kind of access
Apply gravitational funnel pull toward a target pitch. It is categorised as a Execute tool in the Constraint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Constraint MCP server in PolicyLayer and add a rule for constraint_funnel: 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 Constraint. Nothing to install.
constraint_funnel 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 constraint_funnel 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 constraint_funnel. 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.
constraint_funnel is provided by the Constraint MCP server (superinstance/constraint-mcp-server). 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 →