Run the bridge test effects script to verify communication and apply test effects
AI agents invoke run-bridge-test to trigger actions in After Effects 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 executes a script ('run_bridge_test_effects'), which is a form of code execution. While the purpose is testing/verification, script execution in After Effects can trigger side effects (applying effects, modifying layers, changing project state). The effects are likely reversible within an undo operation, but the tool's nature is to execute arbitrary logic.
From the tool's definition Tool description states 'Run the bridge test effects script' — explicitly invokes script execution. 'apply test effects' indicates this operation modifies the After Effects project state through arbitrary script execution.
Documented attack patterns abuse exactly the kind of access run-bridge-test gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and After Effects MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run-bridge-test:
{
"version": "1",
"default": "deny",
"tools": {
"run-bridge-test": {
"limits": [
{
"counter": "run-bridge-test_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run-bridge-test 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.
Run the bridge test effects script to verify communication and apply test effects. It is categorised as a Execute tool in the After Effects MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the After Effects MCP Server MCP server in PolicyLayer and add a rule for run-bridge-test: 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 After Effects MCP Server. Nothing to install.
run-bridge-test 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 run-bridge-test 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 run-bridge-test. 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.
run-bridge-test is provided by the After Effects MCP Server MCP server (thellamainator/after-effects-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from After Effects MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 After Effects MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.