New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

run-bridge-test

Run the bridge test effects script to verify communication and apply test effects

SERVERAos SOURCE@hybridlabor-api/aos
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about run-bridge-test

What does the run-bridge-test tool do? +

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.

How do I enforce a policy on run-bridge-test? +

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.

What risk level is run-bridge-test? +

run-bridge-test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run-bridge-test? +

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.

How do I block run-bridge-test completely? +

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.

What MCP server provides run-bridge-test? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aos's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.