capabilities_query
Read capabilities.query through the Appaloft application operation catalog. Shared with HTTP/API.
This record as markdown: /tools/appaloft-mcp/capabilities-query.md
What capabilities_query does on Appaloft
AI agents call capabilities_query to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
queries | array | Yes |
Parameters from the server's own tool schema.
Why capabilities_query is rated Low
This tool retrieves or queries capability information from the application's operation catalog with no side effects. It is a pure read operation as indicated by the explicit "Read" prefix in the description. The low severity reflects that reading capabilities poses minimal risk—it only exposes metadata about what operations are available, not sensitive data manipulation or destructive actions.
From the tool's definition Tool name "capabilities_query" and description "Read capabilities.query" explicitly indicate a read operation. The phrase "Shared with HTTP/API" suggests querying application capabilities without modification.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs capabilities_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For capabilities_query, this is the rule to start with:
capabilities_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every capabilities_query call is checked against it from then on.
Questions about capabilities_query
Read capabilities.query through the Appaloft application operation catalog. Shared with HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
capabilities_query accepts 1 parameter: queries. Required: queries. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for capabilities_query: 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 Appaloft. Nothing to install.
capabilities_query 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 capabilities_query 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 capabilities_query. 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.
capabilities_query is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue