Search workflows (both classic workflows and Power Automate flows) by name, entity, description, category, or state
AI agents call search-workflows 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 retrieves and searches workflow metadata without executing, modifying, or deleting any workflows. It performs a read-only query operation that returns information about existing workflows. No side effects or state changes occur from using this tool.
From the tool's definition Tool name 'search-workflows' and description 'Search workflows...by name, entity, description, category, or state' indicate a query/retrieval operation with no modification or execution of workflows.
Documented attack patterns abuse exactly the kind of access search-workflows 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 search-workflows:
{
"version": "1",
"default": "deny",
"tools": {
"search-workflows": {}
}
} search-workflows 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.
Search workflows (both classic workflows and Power Automate flows) by name, entity, description, category, or state. 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 search-workflows: 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.
search-workflows 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 search-workflows 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 search-workflows. 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.
search-workflows 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.