AI agents call get_server_status to retrieve information from Work Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves server status and diagnostic metadata. It performs no data modification, deletion, code execution, or financial operations. It is a pure read operation that queries the current state of the server. Status and diagnostic queries have minimal blast radius as they only return observational information about system health and configuration.
From the tool's definition Tool name 'get_server_status' and description indicating retrieval of 'status and diagnostic information' from the Work Memory MCP server.
Documented attack patterns abuse exactly the kind of access get_server_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Work Memory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_server_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_server_status": {}
}
}get_server_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
업무 메모리 MCP 서버의 상태 및 진단 정보 조회. It is categorised as a Read tool in the Work Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Work Memory MCP Server MCP server in PolicyLayer and add a rule for get_server_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 Work Memory MCP Server. Nothing to install.
get_server_status 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_server_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.
Set action: deny in the PolicyLayer policy for get_server_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.
get_server_status is provided by the Work Memory MCP Server MCP server (moontmsai/work-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Work Memory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Work Memory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.