This record as markdown: /tools/io-github-kivanccakmak-yaver/eas-submit.md
What eas_submit does on Yaver
AI agents invoke eas_submit 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 |
|---|---|---|---|
platform | string | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why eas_submit is rated High
This tool triggers an external submission process to app stores (Apple App Store or Google Play Store) via Expo Application Services (EAS). It executes an external operation with significant real-world consequences — publishing an app to a production store.
From the tool's definition Submit to App Store / Play Store via EAS
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs eas_submit 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 eas_submit, this is the rule to start with:
eas_submit 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 eas_submit call is checked against it from then on.
Questions about eas_submit
Submit to App Store / Play Store via EAS. 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.
eas_submit accepts 2 parameters: platform, 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 eas_submit: 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.
eas_submit 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 eas_submit 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 eas_submit. 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.
eas_submit 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