create_journal_statement_view · Sanka MCP Server MCP

WHAT IT DOES

What create_journal_statement_view does on Sanka MCP Server

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

WHY IT NEEDS A POLICY

Why create_journal_statement_view needs a policy

This tool creates new financial statement views, which constitutes data modification in a financial system. It does not delete or move money (thus not Destructive or Financial), but it does reversibly create new financial reporting artifacts.

From the tool's definition Tool name 'create_journal_statement_view' and description indicate creating a new journal view/statement artifact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_journal_statement_view Rate-limited

create_journal_statement_view 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": {
    "create_journal_statement_view": {
      "limits": [
        {
          "counter": "create_journal_statement_view_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 Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about create_journal_statement_view

What does the create_journal_statement_view tool do? +

Create a Sanka journal view for Profit and Loss, Balance Sheet, or Cash Flow from existing journal entries. Use this when the user asks to create a PL/BS/CF view from Sanka journal data. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_journal_statement_view? +

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

What risk level is create_journal_statement_view? +

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

Can I rate-limit create_journal_statement_view? +

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

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

create_journal_statement_view is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.