projects_count
Read projects.count through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/projects-count.md
What projects_count does on Appaloft
AI agents call projects_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.
Why projects_count is rated Low
The tool performs a simple count query on projects, which is a read-only retrieval operation. It returns aggregated data with no ability to modify, delete, or execute arbitrary operations. The low severity reflects minimal blast radius—a count endpoint typically returns numeric data with no sensitive business logic exposure.
From the tool's definition Tool description states 'Read projects.count' which explicitly indicates a read operation that retrieves data without modification. No side effects or state changes are implied.
Attacks that exploit this kind of access
The rule that runs projects_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 projects_count, this is the rule to start with:
projects_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 projects_count call is checked against it from then on.
Questions about projects_count
Read projects.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.
Register the Appaloft MCP server in PolicyLayer and add a rule for projects_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.
projects_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 projects_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 projects_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.
projects_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