get_credits

THE RISK

Low Risk

Why get_credits needs a policy

This tool retrieves account credit information for the user's LeadMagic account. It performs a read-only query to fetch metadata about API usage and available credits. There are no side effects, no data modification, no code execution, and no destructive or financial operations. It is analogous to checking an account balance in a bank dashboard—informational only.

From the tool's definition Tool name 'get_credits' and description 'Check the number of available API credits' indicate querying account balance/status without modification or execution of external operations.

Documented attack patterns abuse exactly the kind of access get_credits gives an agent:

POLICY

How to control get_credits

PolicyLayer is an MCP gateway — it sits between your AI agents and LeadMagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_credits:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_credits": {}
  }
}

get_credits is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register LeadMagic MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More LeadMagic MCP Server tools

Read email_to_profile Find B2B profile URL using work email address. Reverse lookup functionality to discover pr Read find_email Find verified email address based on a person\ Read find_employees Find employees of a specific company. Discover team members, their roles, and contact info Read find_jobs Search for job postings based on various criteria including company, title, location, and Read find_mobile Find mobile phone numbers using profile URL, work email, or personal email. Discover direc Read find_personal_email Find personal email addresses from B2B profile URLs. Useful for reaching contacts through Read find_role Find specific roles/positions within a company. Targeted search for particular job titles Read get_b2b_ad_details Get detailed information about a specific B2B ad including campaign information, creative

All 19 LeadMagic MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_credits

What does the get_credits tool do? +

Check the number of available API credits for your LeadMagic account. Essential for monitoring usage and planning API calls. It is categorised as a Read tool in the LeadMagic MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_credits? +

Register the LeadMagic MCP Server MCP server in PolicyLayer and add a rule for get_credits: 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 LeadMagic MCP Server. Nothing to install.

What risk level is get_credits? +

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

Can I rate-limit get_credits? +

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

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

get_credits is provided by the LeadMagic MCP Server MCP server (leadmagic/leadmagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LeadMagic MCP Server tool call.

Start from LeadMagic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →