build_unstake_tx · Logiqical MCP: Risk & Policy

WHAT IT DOES

What build_unstake_tx does on Logiqical

AI agents invoke build_unstake_tx to trigger actions in Logiqical. 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 build_unstake_tx needs a policy

build_unstake_tx triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_unstake_tx Rate-limited

build_unstake_tx 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": {
    "build_unstake_tx": {
      "limits": [
        {
          "counter": "build_unstake_tx_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 Logiqical, so you can run agents against it safely.

FAQ

Questions about build_unstake_tx

What does the build_unstake_tx tool do? +

Unstake ARENA and claim pending rewards. It is categorised as a Execute tool in the Logiqical MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_unstake_tx? +

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

What risk level is build_unstake_tx? +

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

Can I rate-limit build_unstake_tx? +

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

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

build_unstake_tx is provided by the Logiqical MCP server (logiqical-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.