List your house and property projects. Filter by status, area, or priority. Returns name, status, priority, next step, and budget vs spent.
AI agents call house_projects to retrieve information from Personal Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries personal property project information with no side effects. It is purely a read operation that lists and filters existing data. Low severity because exposure of home project details poses minimal risk compared to financial or destructive operations, though some information sensitivity exists given the personal nature of the data.
From the tool's definition Tool description states 'List your house and property projects' with filtering capabilities and returns data fields (name, status, priority, next step, budget vs spent). No modification, deletion, or execution verbs present.
Attacks that exploit this kind of access
List your house and property projects. Filter by status, area, or priority. Returns name, status, priority, next step, and budget vs spent. It is categorised as a Read tool in the Personal Brain MCP Server, which means it retrieves data without modifying state.
Register the Personal Brain MCP server in PolicyLayer and add a rule for house_projects: 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 Personal Brain. Nothing to install.
house_projects 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 house_projects 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 house_projects. 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.
house_projects is provided by the Personal Brain MCP server (phantomts/personal-brain-mcp). 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 →