get_voxel_status

Detect Voxel directory/community plugin. Returns version, post type count, taxonomy count, product type count.

SERVERElementify MCP SOURCEvamerli/elementify-mcp

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/vamerli-elementify-mcp/get-voxel-status.md

WHAT IT DOES

What get_voxel_status does on Elementify MCP

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

RISK

Why get_voxel_status is rated Low

This tool performs a diagnostic read operation that queries metadata about an installed plugin (Voxel) and returns statistical counts. It retrieves and reports information without altering any data, executing code, or triggering external operations. This is purely informational, characteristic of a Read category tool.

From the tool's definition Tool returns version, post type count, taxonomy count, and product type count. The verb 'Detect' and 'Returns' indicate data retrieval with no modification capabilities. No creation, deletion, or execution operations are described.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_voxel_status safely

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

get_voxel_status Allowed

get_voxel_status 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": {
    "get_voxel_status": {}
  }
}

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

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

FAQ

Questions about get_voxel_status

What does the get_voxel_status tool do? +

Detect Voxel directory/community plugin. Returns version, post type count, taxonomy count, product type count. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_voxel_status? +

Register the Elementify MCP server in PolicyLayer and add a rule for get_voxel_status: 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 Elementify MCP. Nothing to install.

What risk level is get_voxel_status? +

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

Can I rate-limit get_voxel_status? +

Yes. Add a rate_limit block to the get_voxel_status 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 get_voxel_status completely? +

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

get_voxel_status is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Elementify, and thousands of servers like it.

This server

All 269 Elementify tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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