get_user_badges
AI agents call get_user_badges to retrieve information from USCardForum 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 user badge information from a Discourse community forum. Badge data is metadata about user achievements or status—retrieval-only with no side effects, data modification, or external execution. The confidence is slightly reduced due to the missing description, but the naming convention and server context strongly indicate a simple read operation.
From the tool's definition Tool name 'get_user_badges' indicates a retrieval operation that fetches badge data associated with a user. The verb 'get' is a read operation.
Attacks that exploit this kind of access
get_user_badges. It is categorised as a Read tool in the USCardForum MCP Server MCP Server, which means it retrieves data without modifying state.
Register the USCardForum MCP Server MCP server in PolicyLayer and add a rule for get_user_badges: 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 USCardForum MCP Server. Nothing to install.
get_user_badges 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_badges 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_badges. 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_badges is provided by the USCardForum MCP Server MCP server (raidenrock/uscardforum-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 →