Search local historical proposal examples. Replace the JSON source with your own indexed archive for production.
AI agents call search_historical_proposals to retrieve information from EPC Tender Screening MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query against a local archive of historical proposals. It retrieves and queries existing data without side effects, modifications, or irreversible actions. The mention of 'Replace the JSON source with your own indexed archive for production' indicates this is a data lookup/retrieval mechanism.
From the tool's definition Tool name 'search_historical_proposals' and description 'Search local historical proposal examples' indicate a read-only retrieval operation.
Attacks that exploit this kind of access
Search local historical proposal examples. Replace the JSON source with your own indexed archive for production. It is categorised as a Read tool in the EPC Tender Screening MCP MCP Server, which means it retrieves data without modifying state.
Register the EPC Tender Screening MCP server in PolicyLayer and add a rule for search_historical_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 EPC Tender Screening MCP. Nothing to install.
search_historical_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 search_historical_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 search_historical_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.
search_historical_proposals is provided by the EPC Tender Screening MCP server (shiverion/epc-tender-screening-mcp-showcase). 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 →