run_performance_benchmark
Run comprehensive performance benchmark
This record as markdown: /tools/aegntic-aegntic-mcp/run-performance-benchmark.md
What run_performance_benchmark does on Obsidian Elite RAG MCP Server
AI agents invoke run_performance_benchmark to trigger actions in Obsidian Elite RAG MCP Server. 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.
Why run_performance_benchmark is rated High
This tool triggers external operations (benchmark execution) rather than merely reading data. While it appears non-destructive and non-financial, benchmarking can consume significant system resources, potentially affecting system performance or generating side effects. Execute category is most appropriate because the tool actively runs operations whose effects depend on runtime arguments and system state.
From the tool's definition Tool name 'run_performance_benchmark' combined with description 'Run comprehensive performance benchmark' indicates execution of a benchmarking operation.
Attacks that exploit this kind of access
The rule that runs run_performance_benchmark safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian Elite RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_performance_benchmark, this is the rule to start with:
run_performance_benchmark stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian Elite RAG MCP Server, apply this rule, and every run_performance_benchmark call is checked against it from then on.
Questions about run_performance_benchmark
Run comprehensive performance benchmark. It is categorised as a Execute tool in the Obsidian Elite RAG MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Obsidian Elite RAG MCP Server MCP server in PolicyLayer and add a rule for run_performance_benchmark: 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 Obsidian Elite RAG MCP Server. Nothing to install.
run_performance_benchmark 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 run_performance_benchmark 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 run_performance_benchmark. 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.
run_performance_benchmark is provided by the Obsidian Elite RAG MCP Server MCP server (aegntic/aegntic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian Elite RAG MCP Server, and thousands of servers like it.
Across the catalogue