340 tools. 137 can modify or destroy data without limits.
27 destructive tools with no built-in limits. Policy required.
Last updated:
Community server · catalogue entry checked 03/10/2026 · full schemas captured for 339 of 340 tools
Running more than one server? Check your whole stack →
Full per-tool breakdown → Model it in the token calculator →
137 of Lovie Company Formation MCP's 340 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Lovie Company Formation MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"accounting_confirm_transfer_pair": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"accounting_cancel_schedule": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"accounting_batch_set_excluded": {
"limits": [
{
"counter": "accounting_batch_set_excluded_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"account_get_account": {
"limits": [
{
"counter": "account_get_account_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
Other MCP servers with similar tools — same risk classification, starter policies for each.
Yes. The Lovie Company Formation MCP server exposes 11 financial tools including accounting_confirm_transfer_pair, accounting_suggest_transfer_pairs, accounting_unpair_transfer. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.
Yes. The Lovie Company Formation MCP server exposes 16 destructive tools including accounting_cancel_schedule, accounting_confirm_statement_match, accounting_delete_journal_entry. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The Lovie Company Formation MCP server has 95 write tools including accounting_batch_set_excluded, accounting_close_period, accounting_create_schedule. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Lovie Company Formation MCP.
340 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 203 are read-only. 137 can modify, create, or delete data.
Register the Lovie Company Formation MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 340 Lovie Company Formation MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
340 Lovie Company Formation MCP tools catalogued and risk-classified — across an index of 46,500+ MCP servers.
These policies come from Lovie Company Formation's registry record.
The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →