Low Risk

get_resource_usage

Get current system resource usage. Returns information about CPU, memory, disk usage, and other system resources being consumed by the backtesting system. Returns: Dictionary containing resource usage information

How to control get_resource_usage ↓

AI agents call get_resource_usage to retrieve information from MaverickMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool only queries and returns system resource metrics. It performs no modifications, deletions, financial transactions, or command execution. It is a straightforward monitoring/observability function. Low severity because the information returned is non-sensitive operational data that cannot be leveraged to cause significant harm even if misused by an AI agent.

From the tool's definition Tool name 'get_resource_usage' and description explicitly states it 'Returns information about CPU, memory, disk usage, and other system resources' — purely informational retrieval with no side effects.

Documented attack patterns abuse exactly the kind of access get_resource_usage gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MaverickMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_resource_usage:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_resource_usage": {}
  }
}

get_resource_usage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MaverickMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_resource_usage tool do? +

Get current system resource usage. Returns information about CPU, memory, disk usage, and other system resources being consumed by the backtesting system. Returns: Dictionary containing resource usage information. It is categorised as a Read tool in the MaverickMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_resource_usage? +

Register the Maverick MCP server in PolicyLayer and add a rule for get_resource_usage: 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 MaverickMCP. Nothing to install.

What risk level is get_resource_usage? +

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

Can I rate-limit get_resource_usage? +

Yes. Add a rate_limit block to the get_resource_usage 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 get_resource_usage completely? +

Set action: deny in the PolicyLayer policy for get_resource_usage. 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 get_resource_usage? +

get_resource_usage is provided by the Maverick MCP server (wshobson/maverick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MaverickMCP tool call.

Deterministic rules across all 54 MaverickMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

54 MaverickMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.