lido_object_easytrack_motion · Lido MCP Server MCP

WHAT IT DOES

What lido_object_easytrack_motion does on Lido MCP Server

AI agents invoke lido_object_easytrack_motion to trigger actions in Lido MCP Server. 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 lido_object_easytrack_motion needs a policy

This tool triggers an on-chain governance action — submitting an objection to an active Easy Track motion on the Lido DAO. This is an external blockchain operation with real effects (registering an objection in the governance contract), making it Execute. It's high severity because it affects live DAO governance processes and could influence protocol decisions if misused by an AI agent.

From the tool's definition Object to an active Easy Track motion

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_object_easytrack_motion Rate-limited

lido_object_easytrack_motion 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": {
    "lido_object_easytrack_motion": {
      "limits": [
        {
          "counter": "lido_object_easytrack_motion_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 Lido MCP Server, so you can run agents against it safely.

FAQ

Questions about lido_object_easytrack_motion

What does the lido_object_easytrack_motion tool do? +

Object to an active Easy Track motion. It is categorised as a Execute tool in the Lido MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lido_object_easytrack_motion? +

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

What risk level is lido_object_easytrack_motion? +

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

Can I rate-limit lido_object_easytrack_motion? +

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

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

lido_object_easytrack_motion is provided by the Lido MCP Server MCP server (the-wunmi/lido-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.