read_agent_spend

Read an agent's settled spend broken down by counterparty and rail over an optional time window.

SERVERLovie Company Formation MCP SOURCElovie

Low RISK CLASS

Category Read

Parameters 30 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/read-agent-spend.md

WHAT IT DOES

What read_agent_spend does on Lovie Company Formation MCP

AI agents call read_agent_spend 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
`since`	string	—
`signerId`	string	—
`companyId`	string	—

Parameters from the server's own tool schema.

RISK

Why read_agent_spend is rated Low

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

read_agent_spend Allowed

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

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

FAQ

Questions about read_agent_spend

What does the read_agent_spend tool do? +

Read an agent's settled spend broken down by counterparty and rail over an optional time window. 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 read_agent_spend accept? +

read_agent_spend accepts 3 parameters: since, signerId, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on read_agent_spend? +

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

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

Can I rate-limit read_agent_spend? +

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

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

read_agent_spend 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

read_input_file on 0gzk → The MCP Attack Database →

Guides

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