Obtenir les informations de crédit de l
AI agents call get_user_credit to retrieve information from Haloscan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves user credit account information from the Haloscan API. It performs a read-only operation with no side effects, no data modification, and no execution of external actions. The incomplete description suggests it's straightforward information retrieval. Misuse would expose credit balance details but poses minimal blast radius as a classified read operation.
From the tool's definition Tool name 'get_user_credit' and description indicate it retrieves credit information without modifying data. The verb 'Obtenir' (French: 'get') indicates data retrieval.
Attacks that exploit this kind of access
Obtenir les informations de crédit de l. It is categorised as a Read tool in the Haloscan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Haloscan MCP Server MCP server in PolicyLayer and add a rule for get_user_credit: 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 Haloscan MCP Server. Nothing to install.
get_user_credit 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_user_credit 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_user_credit. 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_user_credit is provided by the Haloscan MCP Server MCP server (occirank/haloscan-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 →