Fetch the content of a block from a given URL. Use this tool to retrieve the code block content from the authenticated URL.
AI agents call get-block-content 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 fetches or retrieves data (code block content) from a URL with no side effects, reversible modifications, code execution, data deletion, or financial impact. It is a straightforward Read operation. The low severity reflects that retrieving UI component code poses minimal risk even if misused by an AI agent.
From the tool's definition The tool description explicitly states it "Fetch[es] the content" and "retrieve[s] the code block content". No write, execute, destructive, or financial operations are described. The tool is read-only data retrieval.
Documented attack patterns abuse exactly the kind of access get-block-content 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-block-content:
{
"version": "1",
"default": "deny",
"tools": {
"get-block-content": {}
}
}get-block-content 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 content of a block from a given URL. Use this tool to retrieve the code block content from the authenticated URL. 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-block-content: 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-block-content 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-block-content 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-block-content. 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-block-content 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.