New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

service_get_memcached_status

Get Memcached server status and statistics.

SERVERAapanel SOURCEnipunanirmal/aapanel-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/aapanel-mcp/service-get-memcached-status.md

What service_get_memcached_status does on Aapanel

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

Why service_get_memcached_status is rated Low

This tool queries and returns status information about a Memcached service. It performs a read-only operation to fetch statistics and status, with no capability to modify, delete, or execute operations on the Memcached server or underlying system. The low severity reflects minimal risk if misused by an agent, as it only exposes operational metrics.

From the tool's definition Tool name contains 'get' and description states 'Get Memcached server status and statistics' — retrieves monitoring/status data with no modification or side effects.

Questions about service_get_memcached_status

What does the service_get_memcached_status tool do? +

Get Memcached server status and statistics. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on service_get_memcached_status? +

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

What risk level is service_get_memcached_status? +

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

Can I rate-limit service_get_memcached_status? +

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

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

service_get_memcached_status is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Aapanel, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aapanel's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.