transaction_get_categorization_rule

SERVERLovie Company Formation MCP SOURCElovie

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/transaction-get-categorization-rule.md

WHAT IT DOES

What transaction_get_categorization_rule does on Lovie Company Formation MCP

AI agents call transaction_get_categorization_rule to retrieve information from Lovie Company Formation MCP 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
`ruleId`	object	Yes	UUID value wrapper.
`companyId`	object	Yes	UUID value wrapper.

Parameters from the server's own tool schema.

RISK

Why transaction_get_categorization_rule is rated Low

Even though transaction_get_categorization_rule 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 transaction_get_categorization_rule safely

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

transaction_get_categorization_rule Allowed

transaction_get_categorization_rule 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": {
    "transaction_get_categorization_rule": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Lovie Company Formation MCP, apply this rule, and every transaction_get_categorization_rule call is checked against it from then on.

FAQ

Questions about transaction_get_categorization_rule

What does the transaction_get_categorization_rule tool do? +

Read one transaction categorization rule by id: which merchants, amounts or directions it matches, the chart-of-accounts account matching transactions are booked to, and its priority in the evaluation order. Read-only. It is categorised as a Read tool in the Lovie Company Formation MCP MCP Server, which means it retrieves data without modifying state.

What parameters does transaction_get_categorization_rule accept? +

transaction_get_categorization_rule accepts 2 parameters: ruleId, companyId. Required: ruleId, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on transaction_get_categorization_rule? +

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

What risk level is transaction_get_categorization_rule? +

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

Can I rate-limit transaction_get_categorization_rule? +

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

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

transaction_get_categorization_rule is provided by the Lovie Company Formation MCP server (lovie). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Lovie Company Formation, and thousands of servers like it.

This server

All 340 Lovie Company Formation tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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