AI agents call fl_catalog to retrieve information from Flemcee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns static API catalog/documentation information. It has no side effects on FL Studio or any external system — it simply reads and returns metadata about the available API.
From the tool's definition Return the FL Studio API catalog derived from fl-studio-api-stubs
Attacks that exploit this kind of access
Return the FL Studio API catalog derived from fl-studio-api-stubs. It is categorised as a Read tool in the Flemcee MCP Server, which means it retrieves data without modifying state.
Register the Flemcee MCP server in PolicyLayer and add a rule for fl_catalog: 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 Flemcee. Nothing to install.
fl_catalog 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 fl_catalog 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 fl_catalog. 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.
fl_catalog is provided by the Flemcee MCP server (tylerjharden/flemcee). 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 →