Update an existing tenant. Only supplied fields are changed.
AI agents use update_tenant to create or update resources in Lanten MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lanten MCP Server environment.
The tool modifies existing tenant records (Write category) rather than deleting or destructively overwriting them. The update is reversible—fields can be changed back to previous values. Severity is medium because tenant record modifications could impact property management operations and tenant relationships, but the effect is bounded to a single tenant record and reversible.
From the tool's definition Tool name is 'update_tenant' and description states 'Update an existing tenant. Only supplied fields are changed.' This performs reversible modification of tenant data.
Attacks that exploit this kind of access
Update an existing tenant. Only supplied fields are changed. It is categorised as a Write tool in the Lanten MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lanten MCP Server MCP server in PolicyLayer and add a rule for update_tenant: 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 Lanten MCP Server. Nothing to install.
update_tenant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_tenant 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 update_tenant. 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.
update_tenant is provided by the Lanten MCP Server MCP server (lanten-ai/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →