Get Kreato Pro plan pricing and the wallet address to send payment to.
AI agents call get_pro_info to retrieve information from Kreato 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 read-only information about pricing plans and a wallet address. While it relates to financial context (Web3 payments), the tool itself only queries and returns data without executing any transaction, transferring funds, or modifying state. The actual payment is a separate action (send_donation, buy_product, etc.).
From the tool's definition Tool name 'get_pro_info' and description 'Get Kreato Pro plan pricing and the wallet address to send payment to' indicate retrieval of static information (pricing details and a wallet address) with no side effects.
Attacks that exploit this kind of access
Get Kreato Pro plan pricing and the wallet address to send payment to. It is categorised as a Read tool in the Kreato MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kreato MCP Server MCP server in PolicyLayer and add a rule for get_pro_info: 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 Kreato MCP Server. Nothing to install.
get_pro_info 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_pro_info 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_pro_info. 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_pro_info is provided by the Kreato MCP Server MCP server (kreatospace/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 →