Read a single proposal by id. Returns full frontmatter + body.
AI agents call read_proposal to retrieve information from Ebony Enriching without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns proposal data by identifier with no side effects, mutations, or external operations. It is a straightforward query operation that fits the Read category. Severity is low because reading proposal metadata in a research lab notebook context poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'read_proposal' and description states 'Read a single proposal by id. Returns full frontmatter + body.' The verb 'read' and return-only action indicate data retrieval without modification.
Attacks that exploit this kind of access
Read a single proposal by id. Returns full frontmatter + body. It is categorised as a Read tool in the Ebony Enriching MCP Server, which means it retrieves data without modifying state.
Register the Ebony Enriching MCP server in PolicyLayer and add a rule for read_proposal: 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 Ebony Enriching. Nothing to install.
read_proposal 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 read_proposal 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 read_proposal. 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.
read_proposal is provided by the Ebony Enriching MCP server (parkviewlab/ebony-enriching). 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 →