icf_lookup
AI agents call icf_lookup to retrieve information from ICF MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a lookup tool operating against a read-only reference database (WHO ICF classifications). No modification, execution, deletion, or financial operations are possible. The tool retrieves information about ICF codes without changing state. Confidence is slightly reduced because the tool description itself is empty, but the server description and naming convention strongly indicate a Read operation.
From the tool's definition Tool name is 'icf_lookup' and server description indicates tools for 'lookup, search, browsing, and explanation of WHO's International Classification of Functioning, Disability and Health (ICF) codes and qualifiers.' The suffix 'lookup' and the context of…
Attacks that exploit this kind of access
icf_lookup. It is categorised as a Read tool in the ICF MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ICF MCP Server MCP server in PolicyLayer and add a rule for icf_lookup: 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 ICF MCP Server. Nothing to install.
icf_lookup 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 icf_lookup 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 icf_lookup. 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.
icf_lookup is provided by the ICF MCP Server MCP server (stayce/icf-mcp-server). 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 →