goodmem_system_info

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke goodmem_system_info to trigger processes or run actions in Goodmem. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON GOODMEM_SYSTEM_INFO

goodmem_system_info can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

goodmem.yaml

tools:
  goodmem_system_info:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Goodmem policy for all 44 tools.

// DETAILS

Tool Name goodmem_system_info

Category Execute

MCP Server Goodmem MCP Server

Risk Level High

// MORE GOODMEM TOOLS

Destructive goodmem_admin_background_jobs_purge Destructive goodmem_apikeys_delete Destructive goodmem_embedders_delete Destructive goodmem_llms_delete Destructive goodmem_memories_batch_delete Destructive goodmem_memories_delete Destructive goodmem_rerankers_delete Destructive goodmem_spaces_delete

View all 44 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like goodmem_system_info have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Atv build_stake_tx Atv build_unstake_tx Acdp start_local Pentagonal pentagonal_audit Pentagonal pentagonal_compile ACR — Agent Composition Records orient_me

// IN CONTEXT OF HIGH RISK

goodmem_system_info is one of the high-risk operations in Goodmem. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the goodmem_system_info tool do? +

Retrieve server build metadata. It is categorised as a Execute tool in the Goodmem MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on goodmem_system_info? +

Add a rule in your Intercept YAML policy under the tools section for goodmem_system_info. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Goodmem MCP server.

What risk level is goodmem_system_info? +

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

Can I rate-limit goodmem_system_info? +

Yes. Add a rate_limit block to the goodmem_system_info rule in your Intercept 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 goodmem_system_info completely? +

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

goodmem_system_info is provided by the Goodmem MCP server (@pairsystems/goodmem-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.