create-embedded-wallet-app · Openfort MCP Server MCP

WHAT IT DOES

What create-embedded-wallet-app does on Openfort MCP Server

AI agents use create-embedded-wallet-app to create or update resources in Openfort MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openfort MCP Server environment.

WHY IT NEEDS A POLICY

Why create-embedded-wallet-app needs a policy

This tool creates new application resources (embedded wallet apps) within Openfort's infrastructure. Creation of new apps is a Write operation—it modifies system state reversibly and creates new data artifacts. Severity is high because misuse could lead to creation of unauthorized wallet applications that could be exploited for financial purposes, or spam/resource exhaustion of the Openfort platform.

From the tool's definition Tool name is 'create-embedded-wallet-app' and description states it creates 'an embedded wallet app using either the React or React Native SDK'. The verb 'create' indicates data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-embedded-wallet-app Rate-limited

create-embedded-wallet-app stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-embedded-wallet-app": {
      "limits": [
        {
          "counter": "create-embedded-wallet-app_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Openfort MCP Server, so you can run agents against it safely.

FAQ

Questions about create-embedded-wallet-app

What does the create-embedded-wallet-app tool do? +

Create an embedded wallet app using either the React or React Native SDK. It is categorised as a Write tool in the Openfort MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create-embedded-wallet-app? +

Register the Openfort MCP Server MCP server in PolicyLayer and add a rule for create-embedded-wallet-app: 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 Openfort MCP Server. Nothing to install.

What risk level is create-embedded-wallet-app? +

create-embedded-wallet-app is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create-embedded-wallet-app? +

Yes. Add a rate_limit block to the create-embedded-wallet-app 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 create-embedded-wallet-app completely? +

Set action: deny in the PolicyLayer policy for create-embedded-wallet-app. 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 create-embedded-wallet-app? +

create-embedded-wallet-app is provided by the Openfort MCP Server MCP server (openfort-xyz/-deprecated-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.