screen_tender · EPC Tender Screening MCP: Risk & Policy

WHAT IT DOES

What screen_tender does on EPC Tender Screening MCP

AI agents invoke screen_tender to trigger actions in EPC Tender Screening MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why screen_tender needs a policy

This tool orchestrates an end-to-end multi-step workflow that triggers multiple subordinate operations (extraction, matching, matrix generation, memo production). It is an Execute category because it runs a composite pipeline of external operations whose effects depend on the connected tender and company profile inputs.

From the tool's definition "Run the full EPC tender screening workflow: extract requirements, match company profile, generate compliance matrix, and produce bid/no-bid memo."

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

screen_tender Rate-limited

screen_tender stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "screen_tender": {
      "limits": [
        {
          "counter": "screen_tender_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches EPC Tender Screening MCP, so you can run agents against it safely.

FAQ

Questions about screen_tender

What does the screen_tender tool do? +

Run the full EPC tender screening workflow: extract requirements, match company profile, generate compliance matrix, and produce bid/no-bid memo. It is categorised as a Execute tool in the EPC Tender Screening MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on screen_tender? +

Register the EPC Tender Screening MCP server in PolicyLayer and add a rule for screen_tender: 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.

What risk level is screen_tender? +

screen_tender is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit screen_tender? +

Yes. Add a rate_limit block to the screen_tender 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.

How do I block screen_tender completely? +

Set action: deny in the PolicyLayer policy for screen_tender. 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.

What MCP server provides screen_tender? +

screen_tender 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.