publish-customizations

THE RISK

High Risk

Why publish-customizations needs a policy

Publishing customizations triggers an external operation in Dataverse that activates and deploys configuration changes across the environment. This is not a simple write (it doesn't just create/modify data) but rather an operational action that pushes customizations live, potentially affecting all users and system behavior.

From the tool's definition Publish entity customizations or all customizations in Dataverse

Documented attack patterns abuse exactly the kind of access publish-customizations gives an agent:

POLICY

How to control publish-customizations

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 publish-customizations:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "publish-customizations": {
      "limits": [
        {
          "counter": "publish-customizations_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

publish-customizations 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.

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.

RATE-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 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 Write clone-security-role Clone an existing security role into a new role, copying its privileges. Uses CloneAsRole

All 66 PowerPlatform MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in PowerPlatform MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about publish-customizations

What does the publish-customizations tool do? +

Publish entity customizations or all customizations in Dataverse. It is categorised as a Execute tool in the PowerPlatform MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on publish-customizations? +

Register the PowerPlatform MCP server in PolicyLayer and add a rule for publish-customizations: 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 publish-customizations? +

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

Can I rate-limit publish-customizations? +

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

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

publish-customizations 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 →