check_proposals
AI agents call check_proposals to retrieve information from Phenomenai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'check_' prefix typically indicates a query or status check operation. Given the server context (a glossary with proposals, discussions, and terms) and the absence of language indicating modification or deletion, this tool most likely reads proposal information.
From the tool's definition Tool name 'check_proposals' and sibling tools like 'propose_term', 'cite_term', and 'add_to_discussion' indicate a read-only query operation. The tool name pattern and context suggest it retrieves or lists proposal data without modification.
Attacks that exploit this kind of access
check_proposals. It is categorised as a Read tool in the Phenomenai MCP Server, which means it retrieves data without modifying state.
Register the Phenomenai MCP server in PolicyLayer and add a rule for check_proposals: 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 Phenomenai. Nothing to install.
check_proposals 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 check_proposals 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 check_proposals. 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.
check_proposals is provided by the Phenomenai MCP server (phenomenai-org/ai-dictionary-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 →