complete_session · Axiom-hub MCP: Risk & Policy

WHAT IT DOES

What complete_session does on Axiom-hub

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

WHY IT NEEDS A POLICY

Why complete_session needs a policy

Without an explicit description, classification relies on semantic analysis of the tool name and server context. 'Complete' suggests state transition or finalization of a session record—a write operation that modifies but does not delete data. The broader Axiom-hub architecture manages decision memory across sessions, so completing a session probably updates session metadata or status.

From the tool's definition Tool named 'complete_session' with empty description. Sibling tools like 'add_decision', 'add_constraint', and 'check_contradictions' indicate this server manages persistent state and decision memory.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_session Rate-limited

complete_session 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": {
    "complete_session": {
      "limits": [
        {
          "counter": "complete_session_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 Axiom-hub, so you can run agents against it safely.

FAQ

Questions about complete_session

What does the complete_session tool do? +

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

How do I enforce a policy on complete_session? +

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

What risk level is complete_session? +

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

Can I rate-limit complete_session? +

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

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

complete_session is provided by the Axiom-hub MCP server (varunajaytawde28-design/smm-sync). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.