Call a Moleculer action
AI agents invoke moleculer_call_action to trigger actions in Moleculer MCP Server. 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.
Calling a Moleculer action executes arbitrary microservice logic whose effects are entirely dependent on the action invoked. Since the tool provides a generic interface to call any action across the microservice network, it could trigger reads, writes, destructive operations, or financial transactions depending on what actions are registered.
From the tool's definition "Call a Moleculer action" — triggers execution of arbitrary Moleculer microservice actions
Attacks that exploit this kind of access
Call a Moleculer action. It is categorised as a Execute tool in the Moleculer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Moleculer MCP Server MCP server in PolicyLayer and add a rule for moleculer_call_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 Moleculer MCP Server. Nothing to install.
moleculer_call_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 moleculer_call_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 moleculer_call_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.
moleculer_call_action is provided by the Moleculer MCP Server MCP server (moleculerjs/mcp-server). 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 →