exec_status

Read the status and captured output of an existing exec_command without running it again. Use after a polling/connection interruption; the command may still be running.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/exec-status.md

WHAT IT DOES

What exec_status does on Yaver

AI agents call exec_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`exec_id`	string	Yes	Execution ID returned by exec_command.
`device_id`	string	—	The same owned device used for exec_command; omit for local execution.

Parameters from the server's own tool schema.

RISK

Why exec_status is rated Low

Retrieves previously captured command output and status without executing new operations or modifying state.

From the tool's definition Read the status and captured output of an existing exec_command

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs exec_status 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 exec_status, this is the rule to start with:

exec_status Allowed

exec_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "exec_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every exec_status call is checked against it from then on.

FAQ

Questions about exec_status

What does the exec_status tool do? +

Read the status and captured output of an existing exec_command without running it again. Use after a polling/connection interruption; the command may still be running. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does exec_status accept? +

exec_status accepts 2 parameters: exec_id, device_id. Required: exec_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on exec_status? +

Register the Yaver MCP server in PolicyLayer and add a rule for exec_status: 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.

What risk level is exec_status? +

exec_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit exec_status? +

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

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

exec_status 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 678 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →