Get all token deployment IDs for a given deployer address.
AI agents call get_deployer_tokens to retrieve information from Base Token Factory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical deployment data associated with a deployer address. It performs no modifications, deletions, executions, or financial transactions. The operation is purely informational retrieval, making it a Read category tool with low severity even in a blockchain/token context, as it only exposes past deployment records without enabling new deployments or token movements.
From the tool's definition Tool description states 'Get all token deployment IDs for a given deployer address' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all token deployment IDs for a given deployer address. It is categorised as a Read tool in the Base Token Factory MCP Server, which means it retrieves data without modifying state.
Register the Base Token Factory MCP server in PolicyLayer and add a rule for get_deployer_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 Base Token Factory. Nothing to install.
get_deployer_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 get_deployer_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 get_deployer_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.
get_deployer_tokens is provided by the Base Token Factory MCP server (lordbasilaiassistant-sudo/base-token-factory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →