run_cast_command_with_options

run_cast_command_with_options

Server Foundry MCP Project lhemerly/foundry-mcp
Category Execute
Risk class High
Parameters 00 required

What run_cast_command_with_options does on Foundry MCP Project

AI agents invoke run_cast_command_with_options to trigger actions in Foundry MCP Project. 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.

Why run_cast_command_with_options needs a policy

The tool runs cast commands with configurable options, which is Execute-category behavior—it triggers external operations (blockchain interactions, contract calls) whose effects depend on the command arguments supplied. While not inherently Destructive or Financial, cast can be used for financial operations (sending ETH/tokens) or state-altering calls.

From the tool's definition Tool name 'run_cast_command_with_options' indicates execution of cast commands (Foundry's low-level CLI tool for blockchain interactions). The server context shows this MCP enables interaction with Foundry development tools.

Questions about run_cast_command_with_options

What does the run_cast_command_with_options tool do? +

run_cast_command_with_options. It is categorised as a Execute tool in the Foundry MCP Project MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_cast_command_with_options? +

Register the Foundry MCP Project MCP server in PolicyLayer and add a rule for run_cast_command_with_options: 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 Foundry MCP Project. Nothing to install.

What risk level is run_cast_command_with_options? +

run_cast_command_with_options is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_cast_command_with_options? +

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

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

run_cast_command_with_options is provided by the Foundry MCP Project MCP server (lhemerly/foundry-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

run_cast_command_with_options is one line of Foundry MCP Project's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.