get_lms_status
Detect active LMS plugin (LearnDash, Tutor LMS, LifterLMS). Returns plugin name, version, course count.
This record as markdown: /tools/vamerli-elementify-mcp/get-lms-status.md
What get_lms_status does on Elementify MCP
AI agents call get_lms_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.
Why get_lms_status is rated Low
This tool queries the state of installed WordPress plugins and retrieves metadata about them. It performs no write operations, does not execute code or commands, does not delete data, and does not involve financial transactions. The blast radius of misuse is minimal—an AI agent could at worst learn which LMS plugin is active and basic statistics about it, which is non-sensitive informational discovery.
From the tool's definition Tool detects and returns information about active LMS plugins (LearnDash, Tutor LMS, LifterLMS) including plugin name, version, and course count. The verb 'Detect' and 'Returns' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_lms_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_lms_status, this is the rule to start with:
get_lms_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every get_lms_status call is checked against it from then on.
Questions about get_lms_status
Detect active LMS plugin (LearnDash, Tutor LMS, LifterLMS). Returns plugin name, version, course count. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.
Register the Elementify MCP server in PolicyLayer and add a rule for get_lms_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.
get_lms_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_lms_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_lms_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_lms_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.
More on Elementify, and thousands of servers like it.
This server
Across the catalogue