AI agents use store_propositions_tool to create or update resources in Alaya — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alaya environment.
The name implies a write operation — storing data into the knowledge base. However, the description is empty, which significantly lowers confidence. Based on sibling tools context (create, append, capture, batch_ingest all write to the vault), this tool likely writes proposition data. Severity is medium as it modifies the knowledge vault but is likely reversible (sibling tool 'delete_note_tool' exists for reversal).
From the tool's definition Tool name 'store_propositions_tool' suggests storing/writing propositions (claims or statements) to the knowledge vault.
Attacks that exploit this kind of access
store_propositions_tool. It is categorised as a Write tool in the Alaya MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alaya MCP server in PolicyLayer and add a rule for store_propositions_tool: 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 Alaya. Nothing to install.
store_propositions_tool 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 store_propositions_tool 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 store_propositions_tool. 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.
store_propositions_tool is provided by the Alaya MCP server (luke-kucing/alaya). 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 →