List all available Zapier tools with caching
AI agents call list_zapier_tools to retrieve information from OrgFlow 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 displays a list of available Zapier integrations. It performs no side effects, creates no data, executes no code, deletes nothing, and commits no financial obligations. The caching mechanism is an implementation detail that does not change the fundamental read-only nature of the operation. Blast radius is minimal—the worst outcome is information disclosure about available tools.
From the tool's definition Tool name 'list_zapier_tools' and description 'List all available Zapier tools with caching' indicate a retrieval/query operation that enumerates available tools without modifying or executing anything.
Attacks that exploit this kind of access
List all available Zapier tools with caching. It is categorised as a Read tool in the OrgFlow MCP MCP Server, which means it retrieves data without modifying state.
Register the OrgFlow MCP server in PolicyLayer and add a rule for list_zapier_tools: 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 OrgFlow MCP. Nothing to install.
list_zapier_tools 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 list_zapier_tools 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 list_zapier_tools. 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.
list_zapier_tools is provided by the OrgFlow MCP server (sujalpat1810/orgflow_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →