steady_submit_checkin · Steady MCP: Risk & Policy

WHAT IT DOES

What steady_submit_checkin does on Steady MCP

AI agents use steady_submit_checkin to create or update resources in Steady MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Steady MCP environment.

WHY IT NEEDS A POLICY

Why steady_submit_checkin needs a policy

This tool creates new check-in records by submitting form data to app.steady.space. This is a reversible write operation—check-ins can typically be edited or deleted later. It does not execute arbitrary code, delete data irreversibly, or move money. The incomplete description ('Submit today') lowers confidence slightly, but the server description and context make the write intent clear.

From the tool's definition Tool 'steady_submit_checkin' with description 'Submit today' on a server that 'automat[es] the web form through login, team discovery, and check-in submission with previous/next/blockers fields.' The tool creates/submits check-in records to Steady.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

steady_submit_checkin Rate-limited

steady_submit_checkin stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "steady_submit_checkin": {
      "limits": [
        {
          "counter": "steady_submit_checkin_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about steady_submit_checkin

What does the steady_submit_checkin tool do? +

Submit today. It is categorised as a Write tool in the Steady MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on steady_submit_checkin? +

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

What risk level is steady_submit_checkin? +

steady_submit_checkin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit steady_submit_checkin? +

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

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

steady_submit_checkin is provided by the Steady MCP server (sarthak-ignite/steady-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.