richgo_save_obsidian_report · Richgo Finance MCP

WHAT IT DOES

What richgo_save_obsidian_report does on Richgo Finance MCP

AI agents use richgo_save_obsidian_report to create or update resources in Richgo Finance MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Richgo Finance MCP environment.

WHY IT NEEDS A POLICY

Why richgo_save_obsidian_report needs a policy

The tool creates and writes data (a portfolio report) to the user's local file system in Obsidian vault directories. This is reversible (files can be deleted or edited) and does not directly involve financial transactions, code execution on external systems, or data deletion. It falls under Write rather than Execute because it is primarily a file write operation, not arbitrary code/command execution.

From the tool's definition Tool description states it 'saves it inside a user-provided Obsidian vault path' and 'builds a portfolio report and saves it' — this is a create/write operation that modifies the user's file system by adding new content to Obsidian vaults.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

richgo_save_obsidian_report Rate-limited

richgo_save_obsidian_report stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "richgo_save_obsidian_report": {
      "limits": [
        {
          "counter": "richgo_save_obsidian_report_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Richgo Finance MCP, so you can run agents against it safely.

FAQ

Questions about richgo_save_obsidian_report

What does the richgo_save_obsidian_report tool do? +

Use this when the user asks to save a Richgo report to Obsidian, a vault, or a note. It builds a portfolio report and saves it inside a user-provided Obsidian vault path. No personal vault path is hardcoded; provide vaultPath or set RICHGO_OBSIDIAN_VAULT_PATH locally. It is categorised as a Write tool in the Richgo Finance MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on richgo_save_obsidian_report? +

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

What risk level is richgo_save_obsidian_report? +

richgo_save_obsidian_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit richgo_save_obsidian_report? +

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

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

richgo_save_obsidian_report is provided by the Richgo Finance MCP server (reallygood83/rfmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.