Low Risk

get_doc

Fetch the full content of a MetaMask Embedded Wallets documentation page. Use after search_docs to read the actual doc. Tries Algolia, then llms.txt, then GitHub raw MDX as fallbacks.

How to control get_doc ↓

AI agents call get_doc 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.

ParameterTypeRequiredDescription
url string A docs.metamask.io URL, e.g. https://docs.metamask.io/embedded-wallets/sdk/react/

Parameters from the server's own tool schema.

Low Risk

Even though get_doc 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 URL/endpoint input (url)

Documented attack patterns abuse exactly the kind of access get_doc 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 get_doc:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_doc": {}
  }
}

get_doc is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MetaMask Embedded Wallets MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_doc tool do? +

Fetch the full content of a MetaMask Embedded Wallets documentation page. Use after search_docs to read the actual doc. Tries Algolia, then llms.txt, then GitHub raw MDX as fallbacks. It is categorised as a Read tool in the MetaMask Embedded Wallets MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_doc accept? +

get_doc accepts 1 parameter: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_doc? +

Register the MetaMask Embedded Wallets MCP server in PolicyLayer and add a rule for get_doc: 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.

What risk level is get_doc? +

get_doc is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_doc? +

Yes. Add a rate_limit block to the get_doc 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.

How do I block get_doc completely? +

Set action: deny in the PolicyLayer policy for get_doc. 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.

What MCP server provides get_doc? +

get_doc 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.

Enforce policy on every MetaMask Embedded Wallets MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.