load-component

Resolve a UI source (npm, import, or function) into a loadable component

SERVERFrontmcp SOURCEagentfront/frontmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/frontmcp/load-component.md

WHAT IT DOES

What load-component does on Frontmcp

AI agents invoke load-component to trigger actions in Frontmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why load-component is rated High

This tool resolves and loads code from external sources (npm packages, imports, or functions), which constitutes execution of external code/modules. Loading arbitrary npm packages or executing functions at runtime can have significant side effects depending on what is loaded. The 'function' source type especially implies executing arbitrary callable code.

From the tool's definition Resolve a UI source (npm, import, or function) into a loadable component

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs load-component safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For load-component, this is the rule to start with:

load-component Rate-limited

load-component stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "load-component": {
      "limits": [
        {
          "counter": "load-component_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every load-component call is checked against it from then on.

FAQ

Questions about load-component

What does the load-component tool do? +

Resolve a UI source (npm, import, or function) into a loadable component. It is categorised as a Execute tool in the Frontmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on load-component? +

Register the Front MCP server in PolicyLayer and add a rule for load-component: 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 Frontmcp. Nothing to install.

What risk level is load-component? +

load-component is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit load-component? +

Yes. Add a rate_limit block to the load-component 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 load-component completely? +

Set action: deny in the PolicyLayer policy for load-component. 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 load-component? +

load-component is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools → High-risk tools on this server →

Across the catalogue

load_script on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →