Get all observations saved in the separate file for a given projectId.
AI agents call get_project_observations to retrieve information from Xgmem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored observations from a project's knowledge graph without modifying, deleting, or executing any operations. It is a pure read operation that queries existing data. The low severity reflects that unauthorized access to observations would be a data exposure risk, but the tool itself performs no destructive, financial, or executable actions.
From the tool's definition Tool name 'get_project_observations' and description 'Get all observations saved in the separate file for a given projectId' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_project_observations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xgmem, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_observations:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_observations": {}
}
} get_project_observations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all observations saved in the separate file for a given projectId. It is categorised as a Read tool in the Xgmem MCP Server, which means it retrieves data without modifying state.
Register the Xgmem MCP server in PolicyLayer and add a rule for get_project_observations: 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 Xgmem. Nothing to install.
get_project_observations 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 get_project_observations 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 get_project_observations. 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.
get_project_observations is provided by the Xgmem MCP server (meetdhanani17/xgmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xgmem, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Xgmem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.