list_users_with_badge
AI agents call list_users_with_badge 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.
Listing users who have earned specific badges is a retrieval operation with no side effects. It retrieves information from the Discourse forum database without modifying, deleting, or executing actions. The empty description lowers confidence slightly, but the naming pattern and context of peer tools strongly indicate this is a Read category function for querying forum metadata.
From the tool's definition Tool name is 'list_users_with_badge' which indicates a retrieval/query operation. The sibling tools on this server include read-only operations like 'get_categories', 'get_hot_topics', 'get_new_topics', 'get_top_topics', and 'get_notifications'.
Attacks that exploit this kind of access
list_users_with_badge. 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 list_users_with_badge: 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.
list_users_with_badge 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 list_users_with_badge 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 list_users_with_badge. 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.
list_users_with_badge 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 →