Search or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io). Use for troubleshooting real user issues, finding workarounds, and checking if an issue is known. Provide a query to search or a topic_id to read the full discussion.
AI agents call search_community to retrieve information from MetaMask Embedded Wallets MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | — | Search query, e.g. 'popup blocked safari', 'JWT error', 'Android unstable connection' |
topic_id | integer | — | Discourse topic ID to fetch the full discussion thread |
Parameters from the server's own tool schema.
Even though search_community only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts freeform code/query input (query)
Documented attack patterns abuse exactly the kind of access search_community gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MetaMask Embedded Wallets MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_community:
{
"version": "1",
"default": "deny",
"tools": {
"search_community": {}
}
}search_community is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io). Use for troubleshooting real user issues, finding workarounds, and checking if an issue is known. Provide a query to search or a topic_id to read the full discussion. It is categorised as a Read tool in the MetaMask Embedded Wallets MCP MCP Server, which means it retrieves data without modifying state.
search_community accepts 2 parameters: query, topic_id. The full parameter table on this page comes from the server's own tool schema.
Register the MetaMask Embedded Wallets MCP server in PolicyLayer and add a rule for search_community: 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 MetaMask Embedded Wallets MCP. Nothing to install.
search_community 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_community 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_community. 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_community is provided by the MetaMask Embedded Wallets MCP server (web3auth/integrate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 MetaMask Embedded Wallets MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 MetaMask Embedded Wallets MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.