perps_auth_submit · Logiqical MCP: Risk & Policy

WHAT IT DOES

What perps_auth_submit does on Logiqical

AI agents invoke perps_auth_submit 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 perps_auth_submit needs a policy

This tool submits a cryptographically signed authentication payload to a perpetuals trading system. Submitting signed auth steps triggers external operations on-chain or on a trading platform. While it's an auth/authentication action rather than a direct trade or fund movement, it enables access to perpetuals trading infrastructure which can lead to financial operations.

From the tool's definition Submit signed EIP-712 payload for a perps auth step

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

perps_auth_submit Rate-limited

perps_auth_submit 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": {
    "perps_auth_submit": {
      "limits": [
        {
          "counter": "perps_auth_submit_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 perps_auth_submit

What does the perps_auth_submit tool do? +

Submit signed EIP-712 payload for a perps auth step. 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 perps_auth_submit? +

Register the Logiqical MCP server in PolicyLayer and add a rule for perps_auth_submit: 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 perps_auth_submit? +

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

Can I rate-limit perps_auth_submit? +

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

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

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