read_contact

Read full details of a contact by ID including all emails, phones, and addresses.

SERVERIconnect SOURCEiconnect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/read-contact.md

WHAT IT DOES

What read_contact does on Iconnect

AI agents call read_contact to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why read_contact is rated Low

This tool retrieves contact information from the Apple ecosystem without creating, modifying, or deleting data. It has no side effects beyond querying and returning existing data. The severity is low because while contact data is personal information, reading it does not expose direct harm vectors like financial loss, code execution, or data destruction.

From the tool's definition Tool name 'read_contact' and description 'Read full details of a contact by ID including all emails, phones, and addresses' explicitly indicates data retrieval with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_contact safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_contact, this is the rule to start with:

read_contact Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every read_contact call is checked against it from then on.

FAQ

Questions about read_contact

What does the read_contact tool do? +

Read full details of a contact by ID including all emails, phones, and addresses. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_contact? +

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

What risk level is read_contact? +

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

Can I rate-limit read_contact? +

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

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

read_contact is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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