This record as markdown: /tools/io-github-kivanccakmak-yaver/pod-install.md
What pod_install does on Yaver
AI agents invoke pod_install to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why pod_install is rated High
pod install is a CocoaPods command that executes a dependency resolution and installation process on the local environment. It runs external tooling, modifies the project's Pods directory and Podfile.lock, and can trigger network downloads. This fits Execute as it runs an external operation with side effects, though it is generally reversible (medium severity).
From the tool's definition 'Run pod install' — explicitly runs a command (CocoaPods dependency installation process)
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs pod_install safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pod_install, this is the rule to start with:
pod_install 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every pod_install call is checked against it from then on.
Questions about pod_install
Run pod install. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
pod_install accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for pod_install: 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 Yaver. Nothing to install.
pod_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pod_install 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 pod_install. 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.
pod_install is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue