garden_reverseJournalEntry
Reverse a posted manual journal entry (POST /v1/garden/journal-entries/{entry}/reverse)
This record as markdown: /tools/onesi-genesis-mcp/garden-reversejournalentry.md
What garden_reverseJournalEntry does on Genesis
AI agents call garden_reverseJournalEntry 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 |
|---|---|---|---|
body | object | — | |
entry | string | Yes | Journal entry id (je_...) |
Parameters from the server's own tool schema.
Why garden_reverseJournalEntry is rated Low
Even though garden_reverseJournalEntry 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.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs garden_reverseJournalEntry 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 garden_reverseJournalEntry, this is the rule to start with:
garden_reverseJournalEntry 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 Genesis, apply this rule, and every garden_reverseJournalEntry call is checked against it from then on.
Questions about garden_reverseJournalEntry
Reverse a posted manual journal entry (POST /v1/garden/journal-entries/{entry}/reverse). It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.
garden_reverseJournalEntry accepts 2 parameters: body, entry. Required: entry. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for garden_reverseJournalEntry: 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.
garden_reverseJournalEntry 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 garden_reverseJournalEntry 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 garden_reverseJournalEntry. 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.
garden_reverseJournalEntry 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.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue