get_clinks
AI agents call get_clinks to retrieve information from Clink MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a standard convention for read-only data retrieval operations. Within a collaboration platform context, this tool likely retrieves clink records (messages or coordination units) without modifying state. The lack of descriptive text lowers confidence slightly, but the naming pattern and absence of any write/destructive keywords in the name support a Read classification.
From the tool's definition Tool name 'get_clinks' suggests a data retrieval operation consistent with the server's messaging and project coordination functions.
Attacks that exploit this kind of access
get_clinks. It is categorised as a Read tool in the Clink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Clink MCP Server MCP server in PolicyLayer and add a rule for get_clinks: 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 Clink MCP Server. Nothing to install.
get_clinks 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 get_clinks 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 get_clinks. 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.
get_clinks is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →