Query reverse dependencies — which targets depend on the given target.
AI agents call bazel_ios_rdeps to retrieve information from XcodeBazelMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a dependency query operation, which is fundamentally a read action that retrieves data about the Bazel build graph. It has no side effects, does not execute code, does not modify data, and does not delete anything. The query semantics align with the Read category for tools that retrieve or query data without side effects.
From the tool's definition Tool name and description indicate it 'Query reverse dependencies — which targets depend on the given target.' This is a read-only query operation that retrieves dependency information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access bazel_ios_rdeps gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XcodeBazelMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bazel_ios_rdeps:
{
"version": "1",
"default": "deny",
"tools": {
"bazel_ios_rdeps": {}
}
}bazel_ios_rdeps is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query reverse dependencies — which targets depend on the given target. It is categorised as a Read tool in the XcodeBazelMCP MCP Server, which means it retrieves data without modifying state.
Register the XcodeBazel MCP server in PolicyLayer and add a rule for bazel_ios_rdeps: 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 XcodeBazelMCP. Nothing to install.
bazel_ios_rdeps is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bazel_ios_rdeps 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 bazel_ios_rdeps. 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.
bazel_ios_rdeps is provided by the XcodeBazel MCP server (xcodebazelmcp/xcodebazelmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from XcodeBazelMCP, 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.
117 XcodeBazelMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.