get_status

Get a comprehensive status overview of all locks including battery levels, lock states, and any issues

Server Seam MCP Server keithah/seam-mcp
Category Read
Risk class Low
Parameters 00 required

What get_status does on Seam MCP Server

AI agents call get_status to retrieve information from Seam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_status needs a policy

This tool queries and returns information about lock states, battery levels, and issues without creating, modifying, deleting, or executing any changes. It is purely informational (Read category). Even in a smart lock context, status queries pose minimal risk as they cause no physical lock changes or access modifications. Severity is low because misuse only exposes lock status information, not physical access.

From the tool's definition Tool named 'get_status' that 'Get[s] a comprehensive status overview of all locks including battery levels, lock states, and any issues' — retrieves data about lock status with no modifications or side effects.

Questions about get_status

What does the get_status tool do? +

Get a comprehensive status overview of all locks including battery levels, lock states, and any issues. It is categorised as a Read tool in the Seam MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_status? +

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

What risk level is get_status? +

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

Can I rate-limit get_status? +

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

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

get_status is provided by the Seam MCP Server MCP server (keithah/seam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.