claims_mark-stealable · Ruflo MCP: Risk & Policy

WHAT IT DOES

What claims_mark-stealable does on Ruflo

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

WHY IT NEEDS A POLICY

Why claims_mark-stealable needs a policy

This tool creates or modifies access control state ('mark as stealable') reversibly, making it Write category. Severity is high because misconfiguration could allow unauthorized agents to access privileged operations (file-system, code execution) by incorrectly marking issues as stealable.

From the tool's definition Tool name 'claims_mark-stealable' and description states 'Mark an issue as stealable by other agents' — this modifies permission/capability state.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

claims_mark-stealable Rate-limited

claims_mark-stealable 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": {
    "claims_mark-stealable": {
      "limits": [
        {
          "counter": "claims_mark-stealable_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 Ruflo, so you can run agents against it safely.

FAQ

Questions about claims_mark-stealable

What does the claims_mark-stealable tool do? +

Mark an issue as stealable by other agents Use when nothing native covers per-agent capability gating — Claude Code agents have file-system access by default. Pair claims_grant + claims_check before letting an agent run privileged ops. For trusted in-session work, no claims call is needed. It is categorised as a Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on claims_mark-stealable? +

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

What risk level is claims_mark-stealable? +

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

Can I rate-limit claims_mark-stealable? +

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

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

claims_mark-stealable is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.