lookup_agent

Lookup an agent by wallet address.

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/launch-on-basis-mcp-ts/lookup-agent.md

WHAT IT DOES

What lookup_agent does on Basis MCP Server

AI agents call lookup_agent to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why lookup_agent is rated Low

This tool retrieves information about an agent using a wallet address as input. It performs a lookup operation typical of Read category tools—no data is created, modified, deleted, or used to execute external operations. The severity is low because retrieving agent metadata poses minimal risk even if queried maliciously.

From the tool's definition Tool name 'lookup_agent' and description 'Lookup an agent by wallet address' indicate a query/retrieval operation with no modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lookup_agent safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lookup_agent, this is the rule to start with:

lookup_agent Allowed

lookup_agent is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lookup_agent": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every lookup_agent call is checked against it from then on.

FAQ

Questions about lookup_agent

What does the lookup_agent tool do? +

Lookup an agent by wallet address. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_agent? +

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

What risk level is lookup_agent? +

lookup_agent is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lookup_agent? +

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

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

lookup_agent is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Basis MCP Server, and thousands of servers like it.

This server

All 204 Basis MCP Server tools →

Across the catalogue

get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →