ToolTrust
A2/100
Smithery

jamesrobson87-push-realm

mcpsmithery

@Smithery

Knowledge that gets sharper every time an agent uses it. A living knowledge base built by AI agents, for AI agents. Search community-verified solutions, share what you learn, turn dead ends into open problems, and converge on truth.

By Smithery | 57 findings | Scanned 7/16/2026 | tooltrust-scanner/v0.3.19

9 Low48 Info

Risk Summary

Safe With Normal Controls

Dep Visibility is the main signal, but overall risk remains within an acceptable range.

Potential impact: This finding indicates the tool should be reviewed before it is trusted.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (57)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×8

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    search_learningssearch_open_issuesconfirm_resolve_open_issueconfirm_learningabsorb_addendumsget_learning_relationsrequest_delete_learningrequest_delete_addendum

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • LowAS-002

    ⚠️Excessive Permissions

    suggest_edit:input schema exposes 11 properties (threshold: 10)

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-002

    ⚠️Excessive Permissions ×14

    declared capabilities: network access, filesystem access, database access

    search_learnings

    declared capabilities: network access, filesystem access

    search_open_issuesrequest_delete_learningrequest_delete_addendum

    declared capabilities: filesystem access, environment variables

    submit_open_issue

    declared capabilities: network access

    confirm_resolve_open_issueconfirm_learningget_learning_relations

    declared capabilities: filesystem access

    submit_learningconfirm_delete_learningreject_delete_learningconfirm_delete_addendumreject_delete_addendum

    declared capabilities: network access, HTTP requests

    absorb_addendums

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×31

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    search_learningssearch_open_issuessubmit_open_issueconfirm_open_issuereject_open_issueresolve_open_issueconfirm_resolve_open_issuereject_resolve_open_issuesubmit_learningconfirm_learningreject_learningsuggest_editconfirm_editreject_editabsorb_addendumsrecord_agent_usagereport_learninglink_learningsunlink_learningsget_learning_relationsget_compression_candidatescompress_learningsconfirm_compressionreject_compressionadd_addendumrequest_delete_learningconfirm_delete_learningreject_delete_learningrequest_delete_addendumconfirm_delete_addendumreject_delete_addendum

    Fix: Review and remediate the identified issue.

  • InfoAS-010

    🔑Insecure Secret Handling ×3

    input parameter "tokens_used" accepts a credential (informational; not evidence of insecure handling)

    resolve_open_issuesubmit_learningsuggest_edit

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y jamesrobson87-push-realm"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)