trustgo_login · AgentGo MCP Service MCP: Risk & Policy

WHAT IT DOES

What trustgo_login does on AgentGo MCP Service

AI agents invoke trustgo_login to trigger actions in AgentGo MCP Service. 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 trustgo_login needs a policy

This tool performs an external authentication action against the TrustGo platform, creating a session or token. It is not a simple read, nor does it delete data or move money. It executes an external operation (login/auth flow) whose effects (session creation, access grants) depend on the provided signature argument, placing it in the Execute category.

From the tool's definition 'login to TrustGo with EVM signature' — triggers an authentication/session operation on an external platform using cryptographic signing (EIP-191 protocol)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trustgo_login Rate-limited

trustgo_login 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": {
    "trustgo_login": {
      "limits": [
        {
          "counter": "trustgo_login_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 AgentGo MCP Service, so you can run agents against it safely.

FAQ

Questions about trustgo_login

What does the trustgo_login tool do? +

Using EIP-191 protocol to login to TrustGo with EVM signature. It is categorised as a Execute tool in the AgentGo MCP Service MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trustgo_login? +

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

What risk level is trustgo_login? +

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

Can I rate-limit trustgo_login? +

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

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

trustgo_login is provided by the AgentGo MCP Service MCP server (quan3xin/agentgo-mcp-service). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.