Retrieve full details of a single official mirror queue entry by ID. Returns complete information including all mirror versions and linked server details. This tool provides comprehensive information about an official mirror queue entry, including: - Queue item metadata (name, status, timestamps)...
AI agents call get_official_mirror_queue_item to retrieve information from Pulsemcp Cms Admin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data about official mirror queue entries without modifying, deleting, or executing any operations. It is a pure read/retrieval function. The low severity reflects that retrieving queue metadata poses minimal risk even if accessed by an untrusted agent, as it does not alter system state or expose sensitive credentials or payment information.
From the tool's definition Tool name includes 'get_' and description states 'Retrieve full details' and 'Returns complete information' — these are unambiguous retrieval operations with no side effects.
Attacks that exploit this kind of access
Retrieve full details of a single official mirror queue entry by ID. Returns complete information including all mirror versions and linked server details. This tool provides comprehensive information about an official mirror queue entry, including: - Queue item metadata (name, status, timestamps) - All mirror versions with complete server.json data - Linked MCP server details (if linked) - Server linkage consistency status The response includes all fields from the server.json submissions: - Name, version, description - GitHub repository URL - Website URL - Categories and license - Remote endpoints (hosted versions) - Package information (npm, pip, etc.) - Schema version and ingestion metadata Use cases: - Review complete details of a queue entry before taking action - Compare mirror versions to see changes over time - Check linked server details and linkage consistency - Access full server.json data for decision making - Verify remote endpoints and package information. It is categorised as a Read tool in the Pulsemcp Cms Admin MCP Server, which means it retrieves data without modifying state.
Register the Pulsemcp Cms Admin MCP server in PolicyLayer and add a rule for get_official_mirror_queue_item: 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 Pulsemcp Cms Admin. Nothing to install.
get_official_mirror_queue_item 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 get_official_mirror_queue_item 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 get_official_mirror_queue_item. 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.
get_official_mirror_queue_item is provided by the Pulsemcp Cms Admin MCP server (pulsemcp-cms-admin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →