resources_count
Read resources.count through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-count.md
What resources_count does on Appaloft
AI agents call resources_count 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 |
|---|---|---|---|
projectId | string | — | |
environmentId | string | — | |
includePreviewResources | boolean | — |
Parameters from the server's own tool schema.
Why resources_count is rated Low
This tool retrieves a count of resources with no side effects or data modification. The explicit 'Read' designation in the description, combined with the singular purpose of counting (a retrieval operation), places it clearly in the Read category. The low severity reflects the minimal blast radius—an AI agent misusing this tool could at worst enumerate resource counts, which is non-destructive reconnaissance data.
From the tool's definition Tool description explicitly states 'Read resources.count' and operation is a counting/query function with no modification capability.
Attacks that exploit this kind of access
The rule that runs resources_count 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 resources_count, this is the rule to start with:
resources_count 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 resources_count call is checked against it from then on.
Questions about resources_count
Read resources.count through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
resources_count accepts 3 parameters: projectId, environmentId, includePreviewResources. 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 resources_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 Appaloft. Nothing to install.
resources_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 resources_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 resources_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.
resources_count 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