card_get_list_cards
Lists the cards the caller holds in one company: label, last four digits, network, state, spend limit and expiry. Set company_id to the company whose cards to list (get_my_companies lists the ones the user belongs to) — it is required, and a card belongs to exactly one company. Read-only. Never r...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/card-get-list-cards.md
What card_get_list_cards does on Lovie Company Formation MCP
AI agents call card_get_list_cards 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. |
includeCanceled | boolean | — |
Parameters from the server's own tool schema.
Why card_get_list_cards is rated Low
Even though card_get_list_cards 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 card_get_list_cards 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 card_get_list_cards, this is the rule to start with:
card_get_list_cards 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 card_get_list_cards call is checked against it from then on.
Questions about card_get_list_cards
Lists the cards the caller holds in one company: label, last four digits, network, state, spend limit and expiry. Set company_id to the company whose cards to list (get_my_companies lists the ones the user belongs to) — it is required, and a card belongs to exactly one company. Read-only. Never returns another member's card, and the full card number and CVV are never returned by this or any other tool. It is categorised as a Read tool in the Lovie Company Formation MCP MCP Server, which means it retrieves data without modifying state.
card_get_list_cards accepts 2 parameters: companyId, includeCanceled. Required: companyId. 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 card_get_list_cards: 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.
card_get_list_cards 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 card_get_list_cards 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 card_get_list_cards. 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.
card_get_list_cards 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