Fetch the metadata of a block from a given URL. Use this tool to retrieve the block metadata. This will provide the metadata of all the FlyonUI blocks available for use.
AI agents call get-blocks-metadata to retrieve information from FlyonUI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about UI blocks/components from FlyonUI—a fundamentally informational operation. There are no side effects, no data modification, no code execution, and no destructive actions. The tool simply queries and returns existing metadata, making it a Read category risk with low severity.
From the tool's definition Tool description states 'Fetch the metadata of a block' and 'retrieve the block metadata' — both read operations that query metadata without modification.
Documented attack patterns abuse exactly the kind of access get-blocks-metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FlyonUI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-blocks-metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get-blocks-metadata": {}
}
}get-blocks-metadata is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch the metadata of a block from a given URL. Use this tool to retrieve the block metadata. This will provide the metadata of all the FlyonUI blocks available for use. It is categorised as a Read tool in the FlyonUI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FlyonUI MCP Server MCP server in PolicyLayer and add a rule for get-blocks-metadata: 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 FlyonUI MCP Server. Nothing to install.
get-blocks-metadata 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-blocks-metadata 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-blocks-metadata. 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-blocks-metadata is provided by the FlyonUI MCP Server MCP server (themeselection/flyonui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 FlyonUI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 FlyonUI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.