
Agent Guard
io.github.ipezygjPublished by GitHub account ipezygjv0.2.1Updated Oct 24, 2026
Safety checks an agent runs before it acts: package malware, destructive command, secret leak.
Overview
A local safety-check server that lets an assistant screen planned actions for malware, destructive commands, and secret leaks before acting.
- What you can do
- Agent Guard provides pre-action safety checks an agent can run before it executes something. According to its description, it covers three areas: package malware, destructive commands, and secret leaks. It runs as a local process over stdio, so the checks happen on the user's own machine rather than through a remote service.
- When to use it
- Worth adding when an assistant is allowed to install packages, run shell commands, or handle credentials and you want a guardrail step before those actions take effect. It suits setups where the agent's actions carry real risk of damage or exposure.
- Requirements
- Runs as a local process on the user's machine over stdio, installed from the PyPI package agent-tripwire, so a Python runtime and package installation are needed. No authentication, environment variables, or headers are declared. Desktop only; not available as a web executable.
Installation
In SourceWeft
- Open Agent Guard in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.