AI agents use manage_properties to create or update resources in Bookie — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bookie environment.
This tool performs reversible modifications to rental property records in a financial accounting system. Creating and archiving properties are Write operations — they modify the property catalog that supports tax filing (Schedule E). While it affects financial records, it does not move money (Financial), delete irreversibly (Destructive), or execute arbitrary code (Execute).
From the tool's definition Tool description states 'Create, list, or archive rental properties' — create and archive are write operations that modify data structure and state.
Attacks that exploit this kind of access
Create, list, or archive rental properties. Schedule E is filed per property, so rental transactions are tagged with a propertyId (and optional unit) in add_transaction. Non-rental work doesn. It is categorised as a Write tool in the Bookie MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bookie MCP server in PolicyLayer and add a rule for manage_properties: 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 Bookie. Nothing to install.
manage_properties 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 manage_properties 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 manage_properties. 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.
manage_properties is provided by the Bookie MCP server (yuens1002/bookie). 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 →