get_io_performance_metrics
Extract I/O performance metrics including bandwidth, IOPS, and request sizes.
This record as markdown: /tools/io-github-iowarp-adios-mcp/get-io-performance-metrics.md
What get_io_performance_metrics does on CLIO Adios
AI agents call get_io_performance_metrics to retrieve information from CLIO Adios without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_io_performance_metrics is rated Low
This tool queries and retrieves I/O performance data (bandwidth, IOPS, request sizes) from existing BP5 data files. It performs no modifications, deletions, code execution, or financial transactions. The blast radius of misuse is minimal—an agent could only retrieve performance information, which poses no threat to data integrity or system stability.
From the tool's definition Tool name 'get_io_performance_metrics' and description 'Extract I/O performance metrics' indicate data retrieval only. The verbs 'extract' and 'get' are read operations that retrieve performance statistics without modifying or executing external operations.
Attacks that exploit this kind of access
The rule that runs get_io_performance_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_io_performance_metrics, this is the rule to start with:
get_io_performance_metrics 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 CLIO Adios, apply this rule, and every get_io_performance_metrics call is checked against it from then on.
Questions about get_io_performance_metrics
Extract I/O performance metrics including bandwidth, IOPS, and request sizes. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.
Register the CLIO Adios MCP server in PolicyLayer and add a rule for get_io_performance_metrics: 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 CLIO Adios. Nothing to install.
get_io_performance_metrics 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 get_io_performance_metrics 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 get_io_performance_metrics. 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.
get_io_performance_metrics is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CLIO Adios, and thousands of servers like it.
This server
Across the catalogue