Shows the dependency tree of a Swift package and returns structured dependency data.
AI agents call package-show-dependencies to retrieve information from Make without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is a read-only operation that queries and presents the dependency structure of a Swift package. It has no side effects, does not execute code, does not modify or delete data, and does not move money. The worst plausible misuse (an agent requesting dependency information repeatedly) poses minimal risk. Confidence is high because the description clearly indicates a display/retrieval function.
From the tool's definition The tool 'Shows the dependency tree of a Swift package and returns structured dependency data' performs a query/retrieval operation. It reads and displays dependency information without modifying, deleting, or executing any code.
Documented attack patterns abuse exactly the kind of access package-show-dependencies gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for package-show-dependencies:
{
"version": "1",
"default": "deny",
"tools": {
"package-show-dependencies": {}
}
}package-show-dependencies 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.
Shows the dependency tree of a Swift package and returns structured dependency data. It is categorised as a Read tool in the Make MCP Server, which means it retrieves data without modifying state.
Register the Make 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 Make. 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 Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, 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.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.