Get the number of FX plugins on a take.
AI agents call take_fx_get_count to retrieve information from Reaper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply counts and returns the number of FX plugins present on a take. It performs no mutations, executions, or irreversible operations. It is a straightforward read/query operation with minimal security risk.
From the tool's definition Tool name 'take_fx_get_count' and description 'Get the number of FX plugins on a take' indicate a query operation that retrieves information without modifying state.
Documented attack patterns abuse exactly the kind of access take_fx_get_count gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper, and nothing reaches the server without passing your rules. This is the rule we recommend for take_fx_get_count:
{
"version": "1",
"default": "deny",
"tools": {
"take_fx_get_count": {}
}
}take_fx_get_count 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.
Get the number of FX plugins on a take. It is categorised as a Read tool in the Reaper MCP Server, which means it retrieves data without modifying state.
Register the Reaper MCP server in PolicyLayer and add a rule for take_fx_get_count: 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 Reaper. Nothing to install.
take_fx_get_count 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 take_fx_get_count 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 take_fx_get_count. 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.
take_fx_get_count is provided by the Reaper MCP server (twelvetake-studios/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reaper, 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.
158 Reaper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.