Cria e ativa uma nova sessão de profiling.
AI agents invoke iniciar_sessao_profiler to trigger actions in MCP Officegest. 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.
The tool initiates (executes) a profiling session on the backend system. This is an active operation that starts a new process/session rather than merely reading data or writing a record. It triggers ongoing system-level instrumentation, placing it in the Execute category. Severity is medium because misuse could impact server performance or expose profiling data, but it is not directly destructive or financial.
From the tool's definition 'Cria e ativa uma nova sessão de profiling' — creates and activates a new profiling session, triggering an external operation/process on the server
Attacks that exploit this kind of access
Cria e ativa uma nova sessão de profiling. It is categorised as a Execute tool in the MCP Officegest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for iniciar_sessao_profiler: 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.
iniciar_sessao_profiler 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 iniciar_sessao_profiler 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 iniciar_sessao_profiler. 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.
iniciar_sessao_profiler 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 →