Check your current credit balance. Each post generation costs 1 credit.
AI agents call get_credits to retrieve information from PostIdentity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs only a simple balance check/query of account metadata. It is non-destructive, non-executable, and has no financial impact (it only reads balance information, does not transfer funds or commit financial obligations). Blast radius if misused is minimal—an agent could only learn the user's credit balance, not alter it or perform actions with real consequences.
From the tool's definition Tool description states 'Check your current credit balance' — a pure read operation that queries account credit information without modification, creation, deletion, or side effects.
Attacks that exploit this kind of access
Check your current credit balance. Each post generation costs 1 credit. It is categorised as a Read tool in the PostIdentity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostIdentity MCP Server 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 PostIdentity MCP Server. 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 PostIdentity MCP Server MCP server (postidentity/mcp-server). 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 →