Get performance metrics for the VPSA
AI agents call vpsa_get_performance to retrieve information from Zadara Storage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves performance metrics from a storage system. It is a read-only operation that queries existing data without creating, modifying, deleting, or executing any operations. The severity is low because viewing metrics poses minimal risk—it does not expose sensitive data retrieval methods, does not modify storage state, and does not trigger any external operations.
From the tool's definition Tool name 'vpsa_get_performance' and description 'Get performance metrics for the VPSA' indicate retrieval of metrics data with no modification or side effects.
Attacks that exploit this kind of access
Get performance metrics for the VPSA. It is categorised as a Read tool in the Zadara Storage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zadara Storage MCP Server MCP server in PolicyLayer and add a rule for vpsa_get_performance: 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 Zadara Storage MCP Server. Nothing to install.
vpsa_get_performance 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 vpsa_get_performance 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 vpsa_get_performance. 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.
vpsa_get_performance is provided by the Zadara Storage MCP Server MCP server (zadarastorage/zadara-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 →