List all QActions in the application.
AI agents call list_actions to retrieve information from Qt Pilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only introspection tool that queries the application's action registry to return available QActions. It has no side effects—it does not execute actions, modify data, or perform any operations beyond data retrieval. The blast radius of misuse is minimal since listing available actions poses no security or operational risk.
From the tool's definition Tool name 'list_actions' combined with description 'List all QActions in the application' indicates a retrieval operation that enumerates UI actions without modifying application state or triggering those actions.
Documented attack patterns abuse exactly the kind of access list_actions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qt Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for list_actions:
{
"version": "1",
"default": "deny",
"tools": {
"list_actions": {}
}
}list_actions 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 all QActions in the application. It is categorised as a Read tool in the Qt Pilot MCP Server, which means it retrieves data without modifying state.
Register the Qt Pilot MCP server in PolicyLayer and add a rule for list_actions: 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 Qt Pilot. Nothing to install.
list_actions 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_actions 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_actions. 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_actions is provided by the Qt Pilot MCP server (neatobandit0/qt-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Qt Pilot, 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.
15 Qt Pilot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.