list_charges

list_charges

Server Green Helix mirni/a2a
Category Read
Risk class Low
Parameters 00 required

What list_charges does on Green Helix

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

Why list_charges needs a policy

Based on naming convention, 'list_charges' appears to retrieve or enumerate charge records without modifying them. However, confidence is moderate (0.7) rather than high because the description is empty, leaving some ambiguity.

From the tool's definition Tool name 'list_charges' with no description provided. The 'list_' prefix conventionally indicates a retrieval/enumeration operation rather than a state-changing action.

Questions about list_charges

What does the list_charges tool do? +

list_charges. It is categorised as a Read tool in the Green Helix MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_charges? +

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

What risk level is list_charges? +

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

Can I rate-limit list_charges? +

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

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

list_charges is provided by the Green Helix MCP server (mirni/a2a). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

list_charges is one line of Green Helix's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.