connect_current_tender_text · EPC Tender Screening MCP

WHAT IT DOES

What connect_current_tender_text does on EPC Tender Screening MCP

AI agents use connect_current_tender_text to create or update resources in EPC Tender Screening MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EPC Tender Screening MCP environment.

WHY IT NEEDS A POLICY

Why connect_current_tender_text needs a policy

This tool creates or modifies state by setting a tender document as 'current' for use by downstream screening tools. It is reversible (a different tender can be persisted later to replace it), so it does not qualify as Destructive. It has no Read-only purpose and does not execute external code or trigger financial operations.

From the tool's definition The tool description states "Persist uploaded/extracted tender text as the current local tender" — the word "Persist" indicates data is being stored or modified in a system state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_current_tender_text Rate-limited

connect_current_tender_text stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_current_tender_text": {
      "limits": [
        {
          "counter": "connect_current_tender_text_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 connect_current_tender_text

What does the connect_current_tender_text tool do? +

Persist uploaded/extracted tender text as the current local tender used by later screening calls. It is categorised as a Write tool in the EPC Tender Screening MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect_current_tender_text? +

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

connect_current_tender_text is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit connect_current_tender_text? +

Yes. Add a rate_limit block to the connect_current_tender_text 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 connect_current_tender_text completely? +

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

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