sf_migrate_aura_to_lwc
Analyzes an Aura component and returns a comprehensive migration guide with Aura-to-LWC concept mappings, key differences, and an optional LWC scaffold. A read-only advisory tool — does not modify the org. auraComponentName: the Aura component name to analyze includeScaffold: whether to generate ...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-migrate-aura-to-lwc.md
What sf_migrate_aura_to_lwc does on Salesforce Metadata Mcp
AI agents call sf_migrate_aura_to_lwc to retrieve information from Salesforce Metadata Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sf_migrate_aura_to_lwc is rated Low
The tool only reads/analyzes an existing Aura component and produces advisory output (migration guide, concept mappings, optional scaffold). It explicitly states it does not modify the org, making it a pure Read operation with minimal risk.
From the tool's definition 'A read-only advisory tool — does not modify the org' and 'Analyzes an Aura component and returns a comprehensive migration guide'
Attacks that exploit this kind of access
The rule that runs sf_migrate_aura_to_lwc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_migrate_aura_to_lwc, this is the rule to start with:
sf_migrate_aura_to_lwc is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_migrate_aura_to_lwc call is checked against it from then on.
Questions about sf_migrate_aura_to_lwc
Analyzes an Aura component and returns a comprehensive migration guide with Aura-to-LWC concept mappings, key differences, and an optional LWC scaffold. A read-only advisory tool — does not modify the org. auraComponentName: the Aura component name to analyze includeScaffold: whether to generate equivalent LWC template, JS, CSS, and meta files. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_migrate_aura_to_lwc: 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 Salesforce Metadata Mcp. Nothing to install.
sf_migrate_aura_to_lwc 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 sf_migrate_aura_to_lwc 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 sf_migrate_aura_to_lwc. 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.
sf_migrate_aura_to_lwc is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue