Fetch the full Markdown documentation for a specific Flet control or topic.
AI agents call get_flet_doc to retrieve information from Flet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves documentation content. It performs a query/fetch operation that returns data without creating, modifying, deleting, or executing anything. There is no capability to modify state, trigger external operations, or affect system resources. The blast radius of misuse is minimal - an AI could retrieve incorrect documentation but cannot cause harm through fetching alone.
From the tool's definition Tool description states it 'Fetch[es] the full Markdown documentation' - a retrieval operation with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access get_flet_doc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Flet, and nothing reaches the server without passing your rules. This is the rule we recommend for get_flet_doc:
{
"version": "1",
"default": "deny",
"tools": {
"get_flet_doc": {}
}
}get_flet_doc 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 full Markdown documentation for a specific Flet control or topic. It is categorised as a Read tool in the Flet MCP Server, which means it retrieves data without modifying state.
Register the Flet MCP server in PolicyLayer and add a rule for get_flet_doc: 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 Flet. Nothing to install.
get_flet_doc 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_flet_doc 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_flet_doc. 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_flet_doc is provided by the Flet MCP server (nwokike/flet-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Flet, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Flet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.