Low Risk

bazel_ios_deps

Query direct dependencies of a Bazel target.

How to control bazel_ios_deps ↓

What bazel_ios_deps does on XcodeBazelMCP

AI agents call bazel_ios_deps 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.

Low Risk

Why bazel_ios_deps needs a policy

This tool queries and retrieves dependency metadata for a Bazel target. The term 'query' and 'dependencies' indicate a read-only retrieval of target information. There are no indications of side effects, code execution, data modification, or destructive operations. The blast radius is minimal—incorrect usage would simply return wrong or no dependency information to the user.

From the tool's definition Tool name 'bazel_ios_deps' and description 'Query direct dependencies of a Bazel target' indicate a query operation that retrieves dependency information without modifying or executing anything.

Documented attack patterns abuse exactly the kind of access bazel_ios_deps gives an agent:

How to control bazel_ios_deps

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_deps:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "bazel_ios_deps": {}
  }
}

bazel_ios_deps is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register XcodeBazelMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about bazel_ios_deps

What does the bazel_ios_deps tool do? +

Query direct dependencies of a Bazel target. It is categorised as a Read tool in the XcodeBazelMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bazel_ios_deps? +

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

What risk level is bazel_ios_deps? +

bazel_ios_deps is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bazel_ios_deps? +

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

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

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

Enforce policy on every XcodeBazelMCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.