hydra_sync_sources · Hydra Bridge MCP: Risk & Policy

WHAT IT DOES

What hydra_sync_sources does on Hydra Bridge

AI agents invoke hydra_sync_sources to trigger actions in Hydra Bridge. 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 IT NEEDS A POLICY

Why hydra_sync_sources needs a policy

This tool triggers an external operation (forced synchronization) against all configured download sources. It does not merely read data—it actively initiates network requests to remote sources to check for and potentially retrieve updated repack listings. This qualifies as Execute since it triggers external operations whose effects depend on the current state of remote sources.

From the tool's definition Force sync all download sources to check for new repacks

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hydra_sync_sources Rate-limited

hydra_sync_sources 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hydra_sync_sources": {
      "limits": [
        {
          "counter": "hydra_sync_sources_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hydra Bridge, so you can run agents against it safely.

FAQ

Questions about hydra_sync_sources

What does the hydra_sync_sources tool do? +

Force sync all download sources to check for new repacks. It is categorised as a Execute tool in the Hydra Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hydra_sync_sources? +

Register the Hydra Bridge MCP server in PolicyLayer and add a rule for hydra_sync_sources: 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.

What risk level is hydra_sync_sources? +

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

Can I rate-limit hydra_sync_sources? +

Yes. Add a rate_limit block to the hydra_sync_sources 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 hydra_sync_sources completely? +

Set action: deny in the PolicyLayer policy for hydra_sync_sources. 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 hydra_sync_sources? +

hydra_sync_sources 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.