Low Risk

request_quote

Compose a Tewdy quote request from the user's description. Returns a deep link to the Tewdy app with all fields pre-filled; the user reviews and clicks publish to actually post the request. This tool deliberately does not auto-post — quote acceptance and payment confirmation always happen on tewd...

Part of the Tewdy server.

request_quote is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TEWDY →

Free to start. No card required.

AI agents call request_quote to retrieve information from Tewdy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though request_quote only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_quote": {}
  }
}

See the full Tewdy policy for all 11 tools.

Get this rule live on your own Tewdy server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TEWDY →

View all 11 tools →

These attack patterns abuse exactly the kind of access request_quote gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so request_quote only ever does what you allow.

SECURE TEWDY →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the request_quote tool do? +

Compose a Tewdy quote request from the user's description. Returns a deep link to the Tewdy app with all fields pre-filled; the user reviews and clicks publish to actually post the request. This tool deliberately does not auto-post — quote acceptance and payment confirmation always happen on tewdy.com via deep link, never in chat. Requires authentication.. It is categorised as a Read tool in the Tewdy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on request_quote? +

Register the Tewdy MCP server in PolicyLayer and add a rule for request_quote: 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 Tewdy. Nothing to install.

What risk level is request_quote? +

request_quote is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit request_quote? +

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

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

request_quote is provided by the Tewdy MCP server (https://mcp.tewdy.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tewdy tool call.

Deterministic rules across all 11 Tewdy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.