This record as markdown: /tools/launch-on-basis-mcp-ts/get-token-comments.md
What get_token_comments does on Basis MCP Server
AI agents call get_token_comments 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.
Why get_token_comments is rated Low
This tool retrieves existing comment data associated with a token on the Basis protocol. The verb 'get' and the read-only nature of fetching comments (no creation, modification, or deletion) places this squarely in the Read category. There is minimal risk from misuse—an AI agent cannot cause harm by retrieving public or semi-public comments.
From the tool's definition Tool name 'get_token_comments' and description 'Get comments on a token' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_token_comments 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 get_token_comments, this is the rule to start with:
get_token_comments is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every get_token_comments call is checked against it from then on.
Questions about get_token_comments
Get comments on a token. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_token_comments: 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.
get_token_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_token_comments 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.
Set action: deny in the PolicyLayer policy for get_token_comments. 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.
get_token_comments 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.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue