run_workshop_action
Run an action from a workshop through the compact MCP surface.
This record as markdown: /tools/mapi-agent-memory/run-workshop-action.md
What run_workshop_action does on Mapi Agent Memory
AI agents invoke run_workshop_action to trigger actions in Mapi Agent Memory. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why run_workshop_action is rated High
This tool triggers execution of workshop actions whose effects depend on the action argument supplied by the AI agent. Without knowing the constraints on what actions can be run, this poses a high risk of unintended side effects or misuse. It is not merely reading or writing data—it is executing operations, placing it in the Execute category.
From the tool's definition Tool name 'run_workshop_action' and description 'Run an action from a workshop through the compact MCP surface' indicate execution of arbitrary workshop actions. The word 'Run' combined with undefined 'action' parameters suggests external operation invocation.
Attacks that exploit this kind of access
The rule that runs run_workshop_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_workshop_action, this is the rule to start with:
run_workshop_action 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every run_workshop_action call is checked against it from then on.
Questions about run_workshop_action
Run an action from a workshop through the compact MCP surface. It is categorised as a Execute tool in the Mapi Agent Memory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for run_workshop_action: 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 Mapi Agent Memory. Nothing to install.
run_workshop_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_workshop_action 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 run_workshop_action. 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.
run_workshop_action is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
Across the catalogue