package-show-dependencies
Shows the dependency tree of a Swift package and returns structured dependency data.
This record as markdown: /tools/io-github-dave-london-build/package-show-dependencies.md
What package-show-dependencies does on Build
AI agents call package-show-dependencies to retrieve information from Build without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why package-show-dependencies is rated Low
This tool queries and displays existing package dependency information without creating, modifying, executing, or deleting anything. It has no side effects beyond reading and presenting data. The low severity reflects that misuse would only expose non-sensitive metadata about project structure.
From the tool's definition Tool name includes 'show' and description states 'Shows the dependency tree... and returns structured dependency data' — purely informational retrieval with no modification or execution of dependencies.
Attacks that exploit this kind of access
The rule that runs package-show-dependencies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For package-show-dependencies, this is the rule to start with:
package-show-dependencies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every package-show-dependencies call is checked against it from then on.
Questions about package-show-dependencies
Shows the dependency tree of a Swift package and returns structured dependency data. It is categorised as a Read tool in the Build MCP Server, which means it retrieves data without modifying state.
Register the Build MCP server in PolicyLayer and add a rule for package-show-dependencies: 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 Build. Nothing to install.
package-show-dependencies 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 package-show-dependencies 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 package-show-dependencies. 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.
package-show-dependencies is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Build, and thousands of servers like it.
This server
Across the catalogue