Get extracted keywords such as blockchain names, network names, software client names, tags, and relation kinds
AI agents call get_keywords to retrieve information from Chains API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries metadata (keywords, names, tags) without any side effects. It performs no data modification, deletion, code execution, or financial operations. The action is purely informational and read-only, matching the 'Read' category definition of retrieving or querying data with no side effects.
From the tool's definition Tool name 'get_keywords' and description 'Get extracted keywords' indicate a retrieval operation. The description lists only data retrieval: 'blockchain names, network names, software client names, tags, and relation kinds'—all read-only queries with no…
Attacks that exploit this kind of access
Get extracted keywords such as blockchain names, network names, software client names, tags, and relation kinds. It is categorised as a Read tool in the Chains API MCP Server, which means it retrieves data without modifying state.
Register the Chains API MCP server in PolicyLayer and add a rule for get_keywords: 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 Chains API. Nothing to install.
get_keywords 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_keywords 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_keywords. 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_keywords is provided by the Chains API MCP server (johnaverse/chains-api). 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 →