create-plugin-step

THE RISK

Medium Risk

Why create-plugin-step needs a policy

This tool creates a new plugin step registration in PowerPlatform/Dataverse. Creating a plugin step is a Write operation as it registers new code execution hooks that respond to platform events. The severity is high because a maliciously configured plugin step could intercept and manipulate data operations across the platform, potentially affecting many records and business processes.

From the tool's definition "Register a new plugin step (SDK message processing step)"

Documented attack patterns abuse exactly the kind of access create-plugin-step gives an agent:

POLICY

How to control create-plugin-step

PolicyLayer is an MCP gateway — it sits between your AI agents and PowerPlatform MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create-plugin-step:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-plugin-step": {
      "limits": [
        {
          "counter": "create-plugin-step_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create-plugin-step 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.

Create a free account and register PowerPlatform MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More PowerPlatform MCP tools

Destructive delete-security-role Delete a security role. Destructive — requires confirm: true to proceed. Destructive remove-security-role-privileges Remove privileges from a security role. Loops RemovePrivilegeRole — each privilege is remo Destructive replace-security-role-privileges Replace the entire set of privileges on a role with the supplied list (ReplacePrivilegesRo Execute cancel-flow-run Cancel a running or waiting flow run. Cannot cancel flows already in a terminal state (Suc Execute resubmit-flow-run Resubmit/retry a failed flow run using the original trigger inputs Execute publish-customizations Publish entity customizations or all customizations in Dataverse Write add-security-role-privileges Append privileges to a security role using AddPrivilegesRole. Existing privileges are pres Write add-solution-component Add a component to a Dataverse solution

All 66 PowerPlatform MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create-plugin-step

What does the create-plugin-step tool do? +

Register a new plugin step (SDK message processing step). It is categorised as a Write tool in the PowerPlatform MCP 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-plugin-step? +

Register the PowerPlatform MCP server in PolicyLayer and add a rule for create-plugin-step: 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 PowerPlatform MCP. Nothing to install.

What risk level is create-plugin-step? +

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

Can I rate-limit create-plugin-step? +

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

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

create-plugin-step is provided by the PowerPlatform MCP server (michsob/powerplatform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PowerPlatform MCP tool call.

Start from PowerPlatform MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →