registar_entrada_loja_wmso
AI agents use registar_entrada_loja_wmso to create or update resources in MCP Officegest — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Officegest environment.
The tool name suggests it registers or records a new entry in a store/warehouse system, which is a reversible data creation action (Write category). The empty description prevents higher confidence assessment. It is not Destructive (no deletion indicated), Execute (no code execution), or Financial (no money movement).
From the tool's definition Tool name 'registar_entrada_loja_wmso' translates to 'register store entry/input' in Portuguese. The '_wmso' suffix likely refers to warehouse/inventory management.
Attacks that exploit this kind of access
registar_entrada_loja_wmso. It is categorised as a Write tool in the MCP Officegest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for registar_entrada_loja_wmso: 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 MCP Officegest. Nothing to install.
registar_entrada_loja_wmso is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the registar_entrada_loja_wmso 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 registar_entrada_loja_wmso. 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.
registar_entrada_loja_wmso is provided by the MCP Officegest MCP server (rubencodex86/officegest-api-v2-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 →