Check your credit balance and see pricing.
AI agents call credits to retrieve information from RespCode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns financial account information (credit balance and pricing). It does not move money, modify data, or execute code. It is a read-only query of account status.
From the tool's definition 'Check your credit balance and see pricing' — retrieves account balance information with no side effects
Attacks that exploit this kind of access
Check your credit balance and see pricing. It is categorised as a Read tool in the RespCode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RespCode MCP Server MCP server in PolicyLayer and add a rule for 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 RespCode MCP Server. Nothing to install.
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 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 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.
credits is provided by the RespCode MCP Server MCP server (respcodeai/respcode-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 →