lmcp_state
Returns a structured snapshot of the LMCP environment: server/tray/teams-proxy versions, detected AI client, cloud relay state, TCC permission states (Calendar/Reminders/Contacts), and a compact summary of which services (Mail/Calendar/Contacts/Teams/OneDrive/Reminders/Notes) are reachable. Fast ...
This record as markdown: /tools/com-local-mcp-local-mcp/lmcp-state.md
What lmcp_state does on Local
AI agents call lmcp_state to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why lmcp_state is rated Low
lmcp_state performs only information retrieval about the local environment state with no side effects. It does not create, modify, delete, execute, or move data. The explicit statement that it is 'passive' and performs no network operations confirms this is a safe Read category tool with minimal security risk if misused by an agent—it merely exposes system configuration and permission state information.
From the tool's definition Tool returns a 'structured snapshot' of LMCP environment state including versions, permissions, and service reachability.
Attacks that exploit this kind of access
The rule that runs lmcp_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lmcp_state, this is the rule to start with:
lmcp_state 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 Local, apply this rule, and every lmcp_state call is checked against it from then on.
Questions about lmcp_state
Returns a structured snapshot of the LMCP environment: server/tray/teams-proxy versions, detected AI client, cloud relay state, TCC permission states (Calendar/Reminders/Contacts), and a compact summary of which services (Mail/Calendar/Contacts/Teams/OneDrive/Reminders/Notes) are reachable. Fast (<500ms), passive — never prompts the user, never opens app windows, never touches the network. Call this when you need to verify the environment is healthy before attempting a tool, or to understand what's installed and accessible. For reporting failures, use report_problem instead — it captures this same snapshot plus logs and submits to the team. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
Register the Local MCP server in PolicyLayer and add a rule for lmcp_state: 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 Local. Nothing to install.
lmcp_state 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 lmcp_state 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 lmcp_state. 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.
lmcp_state is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue