Histórico cronológico de desempenho entre sessões de profiling, com métricas médias.
AI agents call historico_profiler to retrieve information from MCP Officegest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches historical performance data across profiling sessions and computes average metrics. This is a read/query operation with no write, execute, or destructive implications. Severity is low as misuse would only expose internal performance telemetry.
From the tool's definition 'Histórico cronológico de desempenho' (chronological performance history) and 'métricas médias' (average metrics) — purely retrieves historical profiling data with no indication of side effects.
Attacks that exploit this kind of access
Histórico cronológico de desempenho entre sessões de profiling, com métricas médias. 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 historico_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.
historico_profiler 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 historico_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 historico_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.
historico_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 →