historico_profiler

Histórico cronológico de desempenho entre sessões de profiling, com métricas médias.

SERVERMCP Officegest SOURCErubencodex86/officegest-api-v2-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rubencodex86-officegest-api-v2-mcp/historico-profiler.md

WHAT IT DOES

What historico_profiler does on MCP Officegest

AI agents call historico_profiler 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.

RISK

Why historico_profiler is rated Low

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

RECOMMENDED RULE

The rule that runs historico_profiler 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 historico_profiler, this is the rule to start with:

historico_profiler Allowed

historico_profiler is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "historico_profiler": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Officegest, apply this rule, and every historico_profiler call is checked against it from then on.

FAQ

Questions about historico_profiler

What does the historico_profiler tool do? +

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.

How do I enforce a policy on historico_profiler? +

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.

What risk level is historico_profiler? +

historico_profiler is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit historico_profiler? +

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.

How do I block historico_profiler completely? +

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.

What MCP server provides historico_profiler? +

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.

KEEP EXPLORING

More on MCP Officegest, and thousands of servers like it.

This server

All 306 MCP Officegest tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →