sync_source

Re-fetch a source so its catalog reflects the current upstream.

SERVERLudus FastMCP SOURCEtjnull/ludus-fastmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tjnull-ludus-fastmcp/sync-source.md

WHAT IT DOES

What sync_source does on Ludus FastMCP

AI agents call sync_source to retrieve information from Ludus FastMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sync_source is rated Low

Even though sync_source only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sync_source safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sync_source, this is the rule to start with:

sync_source Allowed

sync_source is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_source": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every sync_source call is checked against it from then on.

FAQ

Questions about sync_source

What does the sync_source tool do? +

Re-fetch a source so its catalog reflects the current upstream. It is categorised as a Read tool in the Ludus FastMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sync_source? +

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

What risk level is sync_source? +

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

Can I rate-limit sync_source? +

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

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

sync_source is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ludus Fast, and thousands of servers like it.

This server

All 231 Ludus Fast tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →