obter_cliente_wmso
Obtém os dados de um cliente do WMS pelo identificador composto.
This record as markdown: /tools/rubencodex86-officegest-api-v2-mcp/obter-cliente-wmso.md
What obter_cliente_wmso does on MCP Officegest
AI agents call obter_cliente_wmso to retrieve information from MCP Officegest without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why obter_cliente_wmso is rated Low
The tool retrieves client data from the WMS (Warehouse Management System) by a composite identifier. This is a straightforward read/query operation with no side effects, data modification, or destructive potential.
From the tool's definition Obtém os dados de um cliente do WMS pelo identificador composto — 'Obtém' means 'Gets/Retrieves', indicating a read-only data retrieval operation.
Attacks that exploit this kind of access
The rule that runs obter_cliente_wmso safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Officegest, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For obter_cliente_wmso, this is the rule to start with:
obter_cliente_wmso is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Officegest, apply this rule, and every obter_cliente_wmso call is checked against it from then on.
Questions about obter_cliente_wmso
Obtém os dados de um cliente do WMS pelo identificador composto. It is categorised as a Read tool in the MCP Officegest MCP Server, which means it retrieves data without modifying state.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for obter_cliente_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.
obter_cliente_wmso 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 obter_cliente_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 obter_cliente_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.
obter_cliente_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.
More on MCP Officegest, and thousands of servers like it.
This server
Across the catalogue