gateway_listCreditEntries

Your One credit ledger (GET /v1/credits/entries)

SERVERGenesis SOURCE@onesi/genesis-mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/onesi-genesis-mcp/gateway-listcreditentries.md

WHAT IT DOES

What gateway_listCreditEntries does on Genesis

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

Parameter	Type	Required	Description
`limit`	integer	—	Entries per page (default set by the service)
`before`	string	—	The next_before cursor of the previous page

Parameters from the server's own tool schema.

RISK

Why gateway_listCreditEntries is rated Low

Even though gateway_listCreditEntries only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gateway_listCreditEntries safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gateway_listCreditEntries, this is the rule to start with:

gateway_listCreditEntries Allowed

gateway_listCreditEntries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gateway_listCreditEntries": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every gateway_listCreditEntries call is checked against it from then on.

FAQ

Questions about gateway_listCreditEntries

What does the gateway_listCreditEntries tool do? +

Your One credit ledger (GET /v1/credits/entries). It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.

What parameters does gateway_listCreditEntries accept? +

gateway_listCreditEntries accepts 2 parameters: limit, before. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gateway_listCreditEntries? +

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

What risk level is gateway_listCreditEntries? +

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

Can I rate-limit gateway_listCreditEntries? +

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

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

gateway_listCreditEntries is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 1127 Genesis tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →