AI agents call list_api_tokens to retrieve information from Linode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays API tokens but does not create, modify, delete, or execute any actions. It is purely informational and falls squarely into the Read category. Severity is low because listing tokens is non-destructive, though the information retrieved could have security implications if exposed to unauthorized parties.
From the tool's definition Tool name 'list_api_tokens' and description 'List API tokens associated with your profile' indicate a retrieval operation with no side effects. The verb 'list' is a query operation that fetches existing data without modification.
Documented attack patterns abuse exactly the kind of access list_api_tokens gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_api_tokens:
{
"version": "1",
"default": "deny",
"tools": {
"list_api_tokens": {}
}
}list_api_tokens is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List API tokens associated with your profile. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for list_api_tokens: 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 Linode MCP Server. Nothing to install.
list_api_tokens 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 list_api_tokens 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 list_api_tokens. 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.
list_api_tokens is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.