Show remaining GhostMinutes credits for the authenticated API key.
AI agents call get_credits to retrieve information from GhostMinutes MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply queries and returns the current credit balance associated with an API key. It has no side effects, does not modify data, does not execute external operations, and does not involve financial transactions—it merely reads a data value. The most severe applicable category is Read, with low severity due to minimal blast radius if misused.
From the tool's definition Tool name 'get_credits' and description 'Show remaining GhostMinutes credits' indicate a read-only query operation that retrieves account credit information without modification or execution.
Attacks that exploit this kind of access
Show remaining GhostMinutes credits for the authenticated API key. It is categorised as a Read tool in the GhostMinutes MCP MCP Server, which means it retrieves data without modifying state.
Register the GhostMinutes MCP server in PolicyLayer and add a rule for get_credits: 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 GhostMinutes MCP. Nothing to install.
get_credits 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_credits 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_credits. 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_credits is provided by the GhostMinutes MCP server (rocketech-software-development/ghostminutes-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 →