get_user_reactions
AI agents call get_user_reactions 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 existing user reaction data from the forum. No modification, deletion, code execution, or financial operations are indicated. The primary risk is information disclosure (learning what reactions users have made), which is minimal in a public community forum context. Severity is low because reactions are typically non-sensitive community engagement data.
From the tool's definition Tool name 'get_user_reactions' indicates a retrieval operation (get_*) that queries user reaction data without modifying or deleting anything.
Attacks that exploit this kind of access
get_user_reactions. 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_reactions: 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_reactions 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_reactions 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_reactions. 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_reactions 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 →