speaker_listener_label_propagation

WHAT IT DOES

What speaker_listener_label_propagation does on Neo4j Gds

AI agents invoke speaker_listener_label_propagation to trigger actions in Neo4j Gds. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why speaker_listener_label_propagation needs a policy

The tool triggers execution of a graph algorithm on a Neo4j database. While it appears to be primarily a read/query operation (community detection), it runs computational workloads on the database infrastructure, which classifies it as Execute. The blast radius is medium as misuse could cause heavy resource consumption on the database but does not directly modify or delete data.

From the tool's definition 'run complex graph algorithms on Neo4j databases' and 'executing appropriate parameterised graph algorithms' — the tool executes a graph algorithm (SLLPA) against a Neo4j database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

speaker_listener_label_propagation Rate-limited

speaker_listener_label_propagation stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "speaker_listener_label_propagation": {
      "limits": [
        {
          "counter": "speaker_listener_label_propagation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Neo4j Gds, so you can run agents against it safely.

FAQ

Questions about speaker_listener_label_propagation

What does the speaker_listener_label_propagation tool do? +

The Speaker-Listener Label Propagation Algorithm (SLLPA) is a variation of the Label Propagation algorithm that is able to detect multiple communities per node. It is categorised as a Execute tool in the Neo4j Gds MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on speaker_listener_label_propagation? +

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

What risk level is speaker_listener_label_propagation? +

speaker_listener_label_propagation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit speaker_listener_label_propagation? +

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

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

speaker_listener_label_propagation is provided by the Neo4j Gds MCP server (neo4j-contrib/gds-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.