Fetch SDK source code (type definitions, interfaces, hooks) from the open-source Web3Auth SDK repos. Use for REFERENCE and DEBUGGING only — to verify exact type shapes, constructor signatures, available hooks, and error types. Do NOT use this to discover features; many SDK options are internal or...
AI agents call get_sdk_reference 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 |
|---|---|---|---|
focus | string | — | What kind of source to focus on. 'types' = interfaces/types (default, most useful). 'hooks' = React hooks / Vue composables. 'errors' = error types. 'main-class |
module | string | — | Specific SDK module to fetch, e.g. 'core-types', 'react-hooks', 'modal-types', 'main-class'. Omit to get default type definitions. Call without module first to |
platform | string | — | Target platform SDK to fetch source for |
Parameters from the server's own tool schema.
Even though get_sdk_reference 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.
Documented attack patterns abuse exactly the kind of access get_sdk_reference 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_sdk_reference:
{
"version": "1",
"default": "deny",
"tools": {
"get_sdk_reference": {}
}
}get_sdk_reference 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.
Fetch SDK source code (type definitions, interfaces, hooks) from the open-source Web3Auth SDK repos. Use for REFERENCE and DEBUGGING only — to verify exact type shapes, constructor signatures, available hooks, and error types. Do NOT use this to discover features; many SDK options are internal or legacy. Always use get_example first for integration patterns. It is categorised as a Read tool in the MetaMask Embedded Wallets MCP MCP Server, which means it retrieves data without modifying state.
get_sdk_reference accepts 3 parameters: focus, module, platform. 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 get_sdk_reference: 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.
get_sdk_reference 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_sdk_reference 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_sdk_reference. 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_sdk_reference 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.