This record as markdown: /tools/hybridlabor-api-aos/run-bridge-test.md
What run-bridge-test does on Aos
AI agents invoke run-bridge-test to trigger actions in Aos. 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 run-bridge-test is rated High
This tool executes code (ExtendScript) within After Effects to verify bridge communication and apply test effects. While framed as a diagnostic/test operation, it runs arbitrary effects scripts in the application, which qualifies as Execute rather than Read. The effects applied are reversible (modifiable/removable), so not Destructive.
From the tool's definition 'Run the bridge test effects script' indicates execution of an ExtendScript program within Adobe After Effects. The server description confirms 'ExtendScript execution' as a core capability.
Attacks that exploit this kind of access
The rule that runs run-bridge-test safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run-bridge-test, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every run-bridge-test call is checked against it from then on.
Questions about run-bridge-test
Run the bridge test effects script to verify communication and apply test effects. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos 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 Aos. 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 Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue