is_agent_registered

Check if a wallet is registered as an agent.

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/is-agent-registered.md

WHAT IT DOES

What is_agent_registered does on Basis MCP Server

AI agents call is_agent_registered 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 is_agent_registered is rated Low

This tool performs a simple lookup/query of blockchain state to verify agent registration status. It has no side effects, does not modify data, and does not execute transactions or code. The operation is purely informational, making it a Read category tool with low severity.

From the tool's definition Tool name 'is_agent_registered' and description 'Check if a wallet is registered as an agent' indicate a query operation that retrieves registration status without modifying or executing any transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs is_agent_registered 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 is_agent_registered, this is the rule to start with:

is_agent_registered Allowed

is_agent_registered 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": {
    "is_agent_registered": {}
  }
}

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 is_agent_registered call is checked against it from then on.

FAQ

Questions about is_agent_registered

What does the is_agent_registered tool do? +

Check if a wallet is registered as an agent. 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 is_agent_registered? +

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

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

Can I rate-limit is_agent_registered? +

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

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

is_agent_registered 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 →