Set or clear the executable path for a game
AI agents use hydra_set_executable_path to create or update resources in Hydra Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hydra Bridge environment.
This tool modifies game metadata (executable path) in a reversible manner. It updates configuration without deleting data or executing code directly. The blast radius is medium because incorrect paths could break game launches or point to unintended executables, but the change is easily reversible by setting a correct path or clearing it.
From the tool's definition Tool name 'hydra_set_executable_path' and description 'Set or clear the executable path for a game' indicate modification of game configuration data.
Attacks that exploit this kind of access
Set or clear the executable path for a game. It is categorised as a Write tool in the Hydra Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hydra Bridge MCP server in PolicyLayer and add a rule for hydra_set_executable_path: 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 Hydra Bridge. Nothing to install.
hydra_set_executable_path is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hydra_set_executable_path 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 hydra_set_executable_path. 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.
hydra_set_executable_path is provided by the Hydra Bridge MCP server (kleirrampage45/hydra-bridge). 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 →