search_forum
AI agents call search_forum 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.
Search functionality on forums retrieves and queries data without modifying state. No credentials bypass, financial impact, or destructive operations are implied. The empty description reduces confidence slightly, but the tool name and server context clearly indicate a non-destructive query operation typical of information retrieval in community forums.
From the tool's definition Tool name 'search_forum' indicates a search/query function. Server description states the MCP server provides tools for 'discovering topics, reading content, researching user profiles' with no mention of side effects for this tool.
Attacks that exploit this kind of access
search_forum. 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 search_forum: 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.
search_forum 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 search_forum 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 search_forum. 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.
search_forum is provided by the USCardForum MCP Server MCP server (rhettlong/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 →