Extract structured EPC tender requirements from tender text. Uses current local tender file if configured.
AI agents call extract_tender_requirements 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 reads and parses tender documents to structure their requirements. It performs no side effects, creates no modifications to persistent data, executes no external code, and triggers no financial transactions. It is purely a data extraction and analysis function, fitting the 'Read' category.
From the tool's definition Tool description states 'Extract structured EPC tender requirements from tender text' — a retrieval and analysis operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Extract structured EPC tender requirements from tender text. Uses current local tender file if configured. 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 extract_tender_requirements: 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.
extract_tender_requirements 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 extract_tender_requirements 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 extract_tender_requirements. 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.
extract_tender_requirements 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 →