formation_check_name

CheckName checks company name availability in the selected state

SERVERLovie Company Formation MCP SOURCElovie

Low RISK CLASS

Category Read

Parameters 11 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/formation-check-name.md

WHAT IT DOES

What formation_check_name does on Lovie Company Formation MCP

AI agents call formation_check_name 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
`formationId`	object	Yes	UUID value wrapper.

Parameters from the server's own tool schema.

RISK

Why formation_check_name is rated Low

Even though formation_check_name 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 formation_check_name 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 formation_check_name, this is the rule to start with:

formation_check_name Allowed

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

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 formation_check_name call is checked against it from then on.

FAQ

Questions about formation_check_name

What does the formation_check_name tool do? +

CheckName checks company name availability in the selected state. 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 formation_check_name accept? +

formation_check_name accepts 1 parameter: formationId. Required: formationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on formation_check_name? +

Register the Lovie Company Formation MCP server in PolicyLayer and add a rule for formation_check_name: 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 formation_check_name? +

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

Can I rate-limit formation_check_name? +

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

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

formation_check_name 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_name on Cocktails RAG MCP Server → The MCP Attack Database →

Guides

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