Resolve a saved workflow by id and return a structured execution plan for a single ticker. Each plan entry names a real MCP tool or SOP plus its ticker-substituted arguments; the calling agent invokes them in order, applying any skip_if predicate against the previous step's output. This tool does...
Part of the Valuein — SEC EDGAR Fundamentals & Smart-Money Data server.
Free to start. No card required.
AI agents invoke run_workflow to trigger processes or run actions in Valuein — SEC EDGAR Fundamentals & Smart-Money Data. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
run_workflow can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"run_workflow": {
"limits": [
{
"counter": "run_workflow_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Valuein — SEC EDGAR Fundamentals & Smart-Money Data policy for all 68 tools.
These attack patterns abuse exactly the kind of access run_workflow gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Resolve a saved workflow by id and return a structured execution plan for a single ticker. Each plan entry names a real MCP tool or SOP plus its ticker-substituted arguments; the calling agent invokes them in order, applying any skip_if predicate against the previous step's output. This tool does NOT execute the steps server-side. It plans; the agent runs. Iterate through plan[] in order, call the named tool/SOP with args, accumulate outputs, and apply each step's skip_if (skip the step when the previous output's path equals equals). Workflows are private state owned by the calling user. Sample-tier callers are rejected. Pair with list_workflows (frontend) to discover available workflow_ids.. It is categorised as a Execute tool in the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP server in PolicyLayer and add a rule for run_workflow: 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 Valuein — SEC EDGAR Fundamentals & Smart-Money Data. Nothing to install.
run_workflow 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 run_workflow 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 run_workflow. 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.
run_workflow is provided by the Valuein — SEC EDGAR Fundamentals & Smart-Money Data MCP server (https://mcp.valuein.biz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 68 Valuein — SEC EDGAR Fundamentals & Smart-Money Data tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.