This record as markdown: /tools/abraflexi/contact-get.md
What contact_get does on AbraFlexi
AI agents call contact_get to retrieve information from AbraFlexi without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why contact_get is rated Low
The naming convention 'contact_get' strongly suggests data retrieval without modification. No side effects or irreversible actions are implied. Even if the description were more detailed, a GET operation on contacts would retrieve or query contact records, fitting the Read category. Confidence is slightly reduced due to empty description, but the tool name is sufficiently clear.
From the tool's definition Tool name 'contact_get' indicates retrieval of contact data. Description is empty, so classification relies on naming convention.
Attacks that exploit this kind of access
The rule that runs contact_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AbraFlexi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contact_get, this is the rule to start with:
contact_get 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 AbraFlexi, apply this rule, and every contact_get call is checked against it from then on.
Questions about contact_get
contact_get is a read tool on the AbraFlexi MCP server. It is categorised as a Read tool in the AbraFlexi MCP Server, which means it retrieves data without modifying state.
Register the AbraFlexi MCP server in PolicyLayer and add a rule for contact_get: 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 AbraFlexi. Nothing to install.
contact_get 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 contact_get 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 contact_get. 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.
contact_get is provided by the AbraFlexi MCP server (abraflexi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AbraFlexi, and thousands of servers like it.
This server
Across the catalogue