element_count

Count how many elements match a selector pattern.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-anything/element-count.md

WHAT IT DOES

What element_count does on Mcp Anything

AI agents call element_count to retrieve information from Mcp Anything without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why element_count is rated Low

This tool reads and counts DOM elements matching a selector, returning information without modifying, creating, or deleting data. It is a straightforward query operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'element_count' and description 'Count how many elements match a selector pattern' indicate a query/retrieval operation with no data modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs element_count safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For element_count, this is the rule to start with:

element_count Allowed

element_count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "element_count": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every element_count call is checked against it from then on.

FAQ

Questions about element_count

What does the element_count tool do? +

Count how many elements match a selector pattern. It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on element_count? +

Register the Mcp Anything MCP server in PolicyLayer and add a rule for element_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 Mcp Anything. Nothing to install.

What risk level is element_count? +

element_count is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit element_count? +

Yes. Add a rate_limit block to the element_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.

How do I block element_count completely? +

Set action: deny in the PolicyLayer policy for element_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.

What MCP server provides element_count? +

element_count is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Anything, and thousands of servers like it.

This server

All 261 Mcp Anything tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →