transaction_suggest_transaction_category
Recommend a bookkeeping category for a transaction using the platform classifier agent. Returns ranked taxonomy option codes with confidence and a short rationale; writes nothing. Apply one with CategorizeTransaction.
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/transaction-suggest-transaction-category.md
What transaction_suggest_transaction_category does on Lovie Company Formation MCP
AI agents call transaction_suggest_transaction_category 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 |
|---|---|---|---|
companyId | object | Yes | UUID value wrapper. |
transactionId | object | Yes | UUID value wrapper. |
Parameters from the server's own tool schema.
Why transaction_suggest_transaction_category is rated Low
Even though transaction_suggest_transaction_category 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
The rule that runs transaction_suggest_transaction_category 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_suggest_transaction_category, this is the rule to start with:
transaction_suggest_transaction_category 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 Lovie Company Formation MCP, apply this rule, and every transaction_suggest_transaction_category call is checked against it from then on.
Questions about transaction_suggest_transaction_category
Recommend a bookkeeping category for a transaction using the platform classifier agent. Returns ranked taxonomy option codes with confidence and a short rationale; writes nothing. Apply one with CategorizeTransaction. It is categorised as a Read tool in the Lovie Company Formation MCP MCP Server, which means it retrieves data without modifying state.
transaction_suggest_transaction_category accepts 2 parameters: companyId, transactionId. Required: companyId, transactionId. The full parameter table on this page comes from the server's own tool schema.
Register the Lovie Company Formation MCP server in PolicyLayer and add a rule for transaction_suggest_transaction_category: 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.
transaction_suggest_transaction_category 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 transaction_suggest_transaction_category 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 transaction_suggest_transaction_category. 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.
transaction_suggest_transaction_category 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.
More on Lovie Company Formation, and thousands of servers like it.
This server
Across the catalogue