Check the deployment status of a Printr token across all its target chains. Returns per-chain status (pending, deploying, live, failed), contract addresses, transaction hashes, graduation progress, and cross-chain message details. Use this to monitor a token after creation.
Part of the Printr MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call printr_get_deployments to retrieve information from Printr without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though printr_get_deployments only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
printr_get_deployments:
rules:
- action: allowSee the full Printr policy for all 23 tools.
Check the deployment status of a Printr token across all its target chains. Returns per-chain status (pending, deploying, live, failed), contract addresses, transaction hashes, graduation progress, and cross-chain message details. Use this to monitor a token after creation.. It is categorised as a Read tool in the Printr MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for printr_get_deployments. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Printr MCP server.
printr_get_deployments 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 printr_get_deployments rule in your Intercept 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 Intercept policy for printr_get_deployments. 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.
printr_get_deployments is provided by the Printr MCP server (@printr/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept