get_profile

THE RISK

Low Risk

Why get_profile needs a policy

This tool retrieves user profile data from the database without modifying, deleting, or executing any operations. It is a straightforward read-only query, presenting minimal risk even if called by an AI agent. The instruction to use it first suggests it is a lightweight lookup operation.

From the tool's definition Tool name 'get_profile' and description 'get the user profile from the database' indicate a retrieval operation with no side effects.

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

POLICY

How to control get_profile

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

policy.json

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

get_profile 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 Prospectio MCP API — 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 Prospectio MCP API tools

Write generate_campaign Generate prospecting messages for contacts WITHOUT existing messages as a campaign. Write insert_leads Use this ONLY when the user asks for NEW opportunities/leads or when get/leads returns ins Write upsert_profile Insert or update the user profile into the database. Read get_campaign_by_id Retrieve a specific campaign by its ID. Read get_campaign_messages Retrieve messages for a specific campaign with pagination. Read get_campaign_result Retrieve the full result of a completed campaign generation task. Read get_campaigns Retrieve all campaigns with pagination. Read get_leads ALWAYS USE THIS FIRST to retrieve existing data from the database before searching for new

All 12 Prospectio MCP API 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_profile

What does the get_profile tool do? +

ALWAYS USE THIS FIRST to get the user profile from the database. It is categorised as a Read tool in the Prospectio MCP API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_profile? +

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

What risk level is get_profile? +

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

Can I rate-limit get_profile? +

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

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

get_profile is provided by the Prospectio MCP API MCP server (prospectio-ai/prospectio-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Prospectio MCP API tool call.

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

CHECK YOUR STACK →