Get all plugin assemblies in the environment
AI agents call get-plugin-assemblies to retrieve information from PowerPlatform MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to enumerate plugin assemblies metadata in a PowerPlatform/Dataverse environment. It retrieves information but does not execute code, modify data, delete resources, or trigger financial transactions. The blast radius of misuse is limited to potential information disclosure about available plugins in the environment.
From the tool's definition Tool name 'get-plugin-assemblies' and description 'Get all plugin assemblies in the environment' indicate a retrieval/query operation that lists existing plugin assemblies without modifying, executing, or deleting them.
Documented attack patterns abuse exactly the kind of access get-plugin-assemblies gives an agent:
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 get-plugin-assemblies:
{
"version": "1",
"default": "deny",
"tools": {
"get-plugin-assemblies": {}
}
} get-plugin-assemblies is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all plugin assemblies in the environment. It is categorised as a Read tool in the PowerPlatform MCP MCP Server, which means it retrieves data without modifying state.
Register the PowerPlatform MCP server in PolicyLayer and add a rule for get-plugin-assemblies: 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.
get-plugin-assemblies 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 get-plugin-assemblies 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 get-plugin-assemblies. 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.
get-plugin-assemblies 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.
Start from PowerPlatform MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
66 PowerPlatform MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.