k1_sit · Execution Market MCP: Risk & Policy

WHAT IT DOES

What k1_sit does on Execution Market

AI agents invoke k1_sit to trigger actions in Execution Market. 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 IT NEEDS A POLICY

Why k1_sit needs a policy

This tool triggers a physical action on what appears to be a robot (K1), commanding it to move into a sitting pose. This constitutes executing an external operation with real-world physical effects. It's not Read/Write/Destructive/Financial. Severity is medium because commanding physical hardware to move could cause harm if misused, though it's a 'resting' pose which is relatively benign.

From the tool's definition Bring the K1 to a stable sitting pose (resting position)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

k1_sit Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "k1_sit": {
      "limits": [
        {
          "counter": "k1_sit_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Execution Market, so you can run agents against it safely.

FAQ

Questions about k1_sit

What does the k1_sit tool do? +

Bring the K1 to a stable sitting pose (resting position). It is categorised as a Execute tool in the Execution Market MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on k1_sit? +

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

What risk level is k1_sit? +

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

Can I rate-limit k1_sit? +

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

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

k1_sit is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.