lctx_team_push · Logica Context MCP: Risk & Policy

WHAT IT DOES

What lctx_team_push does on Logica Context

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

WHY IT NEEDS A POLICY

Why lctx_team_push needs a policy

This tool creates or modifies data in a persistent, shared knowledge base. While not destructive (the operation is reversible in principle), it writes data that affects multiple team members' workflows. The severity is medium rather than high because the impact is limited to knowledge/metadata sharing rather than production systems or critical operations, and there are likely safeguards around sensitive content.

From the tool's definition 'Push content to the team knowledge base' indicates creation/modification of shared data via a database backend (Supabase). The tool modifies team-accessible state irreversibly in the sense that once pushed, content is discoverable by others and persists.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lctx_team_push Rate-limited

lctx_team_push 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": {
    "lctx_team_push": {
      "limits": [
        {
          "counter": "lctx_team_push_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 Logica Context, so you can run agents against it safely.

FAQ

Questions about lctx_team_push

What does the lctx_team_push tool do? +

Push content to the team knowledge base (shared via Supabase). Other developers can search it. It is categorised as a Write tool in the Logica Context MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lctx_team_push? +

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

What risk level is lctx_team_push? +

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

Can I rate-limit lctx_team_push? +

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

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

lctx_team_push is provided by the Logica Context MCP server (rovemark/logica-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.