trends_set_enabled_sources · mcp-techTrend MCP

WHAT IT DOES

What trends_set_enabled_sources does on mcp-techTrend

AI agents use trends_set_enabled_sources to create or update resources in mcp-techTrend — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your mcp-techTrend environment.

WHY IT NEEDS A POLICY

Why trends_set_enabled_sources needs a policy

This tool modifies application state by enabling/disabling data sources (arXiv, PubMed, GitHub, FDA, etc.), making it a Write action. Severity is medium because misconfiguration could cause briefings to omit critical medical or regulatory data, potentially affecting decision-making in safety-critical contexts (FDA recalls, medical devices), but the operation is reversible.

From the tool's definition Tool name 'trends_set_enabled_sources' indicates a configuration setter that modifies which data sources are active.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trends_set_enabled_sources Rate-limited

trends_set_enabled_sources 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": {
    "trends_set_enabled_sources": {
      "limits": [
        {
          "counter": "trends_set_enabled_sources_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 mcp-techTrend, so you can run agents against it safely.

FAQ

Questions about trends_set_enabled_sources

What does the trends_set_enabled_sources tool do? +

trends_set_enabled_sources. It is categorised as a Write tool in the mcp-techTrend MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on trends_set_enabled_sources? +

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

What risk level is trends_set_enabled_sources? +

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

Can I rate-limit trends_set_enabled_sources? +

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

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

trends_set_enabled_sources is provided by the mcp-techTrend MCP server (salwks/mcp-techtrend). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.