get_icon_detail_by_prefix_and_name

get icon detail by prefix and svg name

Server PickAPIcon MCP leee62/pickapicon-mcp
Category Read
Risk class Low
Parameters 00 required

What get_icon_detail_by_prefix_and_name does on PickAPIcon MCP

AI agents call get_icon_detail_by_prefix_and_name to retrieve information from PickAPIcon MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_icon_detail_by_prefix_and_name needs a policy

This tool queries and retrieves icon information from a public icon database (Iconify API) without creating, modifying, deleting, or executing anything. It is a simple lookup/fetch operation with no side effects. The blast radius of misuse is minimal—an attacker could only retrieve icon metadata, which is public information. Low severity because icon details are non-sensitive, read-only data.

From the tool's definition Tool description states 'get icon detail' which retrieves SVG icon metadata by prefix and name parameters. The verb 'get' and the read-only nature of retrieving icon details from the Iconify API indicate no data modification, deletion, or external execution.

Questions about get_icon_detail_by_prefix_and_name

What does the get_icon_detail_by_prefix_and_name tool do? +

get icon detail by prefix and svg name. It is categorised as a Read tool in the PickAPIcon MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_icon_detail_by_prefix_and_name? +

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

What risk level is get_icon_detail_by_prefix_and_name? +

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

Can I rate-limit get_icon_detail_by_prefix_and_name? +

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

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

get_icon_detail_by_prefix_and_name is provided by the PickAPIcon MCP server (leee62/pickapicon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.