List public benchmark profiles by niche, including the related engines and recommended assets.
AI agents call list_benchmarks to retrieve information from Quiet Protocol Growth Offense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing benchmark profiles organized by niche, along with associated engines and assets. It performs a query operation with no side effects, reversible changes, code execution, or financial impact.
From the tool's definition Tool name 'list_benchmarks' and description 'List public benchmark profiles' indicate a retrieval operation with no modification, deletion, or execution of code. The action is read-only querying of public data.
Documented attack patterns abuse exactly the kind of access list_benchmarks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Quiet Protocol Growth Offense, and nothing reaches the server without passing your rules. This is the rule we recommend for list_benchmarks:
{
"version": "1",
"default": "deny",
"tools": {
"list_benchmarks": {}
}
} list_benchmarks 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.
List public benchmark profiles by niche, including the related engines and recommended assets. It is categorised as a Read tool in the Quiet Protocol Growth Offense MCP Server, which means it retrieves data without modifying state.
Register the Quiet Protocol Growth Offense MCP server in PolicyLayer and add a rule for list_benchmarks: 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 Quiet Protocol Growth Offense. Nothing to install.
list_benchmarks 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 list_benchmarks 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 list_benchmarks. 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.
list_benchmarks is provided by the Quiet Protocol Growth Offense MCP server (joeroy2027/tqp-site). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Quiet Protocol Growth Offense, 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.
19 Quiet Protocol Growth Offense tools catalogued and risk-classified — across an index of 43,000+ MCP servers.