Low Risk

dedupq_check

Before executing any LLM task, check if an identical or semantically similar task has already been completed. Returns cached result on hit, saving one LLM call. On a miss, execute your task and call dedupq_complete to cache the result for future hits. Costs 1 credit.

Risk signalsAccepts raw HTML/template content (content)

Part of the Plith server.

dedupq_check 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 PLITH →

Free to start. No card required.

AI agents call dedupq_check to retrieve information from Plith 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 dedupq_check 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": {
    "dedupq_check": {}
  }
}

See the full Plith policy for all 15 tools.

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

ENFORCE ON MY PLITH →

View all 15 tools →

These attack patterns abuse exactly the kind of access dedupq_check 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 dedupq_check only ever does what you allow.

SECURE PLITH →

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

What does the dedupq_check tool do? +

Before executing any LLM task, check if an identical or semantically similar task has already been completed. Returns cached result on hit, saving one LLM call. On a miss, execute your task and call dedupq_complete to cache the result for future hits. Costs 1 credit.. It is categorised as a Read tool in the Plith MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dedupq_check? +

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

What risk level is dedupq_check? +

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

Can I rate-limit dedupq_check? +

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

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

dedupq_check is provided by the Plith MCP server (https://plith.ai/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Plith tool call.

Deterministic rules across all 15 Plith 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.