ToolTrust
B19/100
Smithery

garfield-bb-hap-paas2025

mcpsmithery

@Smithery

Trigger workflows, manage worksheets, and collaborate on record discussions. Create, update, and delete records in bulk, generate share links, and get instant pivot summaries for insights. Administer roles, departments, and optionsets to control access and standardize data across your apps.

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

13 High30 Low68 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 (111)

  • HighAS-003

    🔀Scope Mismatch ×13

    tool name "get_record_relations" implies read-only operation but declares exec permission

    get_record_relations

    tool name "get_record_discussions" implies read-only operation but declares exec permission

    get_record_discussions

    tool name "get_role_details" implies read-only operation but declares exec permission

    get_role_details

    tool name "get_workflow_details" implies read-only operation but declares exec permission

    get_workflow_details

    tool name "get_regions" implies read-only operation but declares exec permission

    get_regions

    tool name "find_department" implies read-only operation but declares exec permission

    find_department

    tool name "get_record_logs" implies read-only operation but declares exec permission

    get_record_logs

    tool name "get_record_share_link" implies read-only operation but declares exec permission

    get_record_share_link

    tool name "find_member" implies read-only operation but declares exec permission

    find_member

    tool name "get_worksheet_structure" implies read-only operation but declares exec permission

    get_worksheet_structure

    tool name "get_record_list" implies read-only operation but declares exec permission

    get_record_list

    tool name "get_record_pivot_data" implies read-only operation but declares exec permission

    get_record_pivot_data

    tool name "get_record_details" implies read-only operation but declares exec permission

    get_record_details

    Fix: Ensure tool names, descriptions, and permission declarations are internally consistent. Use explicit naming conventions that fully reflect actual capabilities.

  • LowAS-011

    â„šī¸Missing Rate-Limit / Timeout ×28

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

    trigger_workflowget_record_relationsget_record_discussionsdelete_worksheetupdate_worksheetbatch_delete_recordscreate_roleget_role_detailsget_workflow_detailscreate_recordbatch_create_recordsupdate_recordget_regionsfind_departmentget_record_logsbatch_update_recordsremove_member_from_roleget_record_share_linkdelete_roledelete_recordfind_memberleave_all_rolesget_worksheet_structureget_record_listget_record_pivot_dataget_record_detailscreate_worksheetadd_member_to_role

    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 ×2

    input schema exposes 13 properties (threshold: 10)

    get_record_list

    input schema exposes 11 properties (threshold: 10)

    get_record_pivot_data

    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 ×31

    declared capabilities: code/command execution

    trigger_workflowget_record_relationsget_record_discussionsget_role_detailsget_workflow_detailsget_regionsfind_departmentget_record_logsget_record_share_linkfind_memberleave_all_rolesget_worksheet_structureget_record_listget_record_detailsadd_member_to_role

    declared capabilities: code/command execution, filesystem access

    delete_worksheetupdate_worksheetbatch_delete_recordscreate_rolecreate_recordbatch_create_recordsupdate_recordbatch_update_recordsremove_member_from_roledelete_roledelete_recordcreate_worksheet

    declared capabilities: filesystem access

    delete_optionsetcreate_optionsetupdate_optionset

    declared capabilities: code/command execution, database access

    get_record_pivot_data

    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 ×36

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

    trigger_workflowget_record_relationsget_record_discussionsdelete_worksheetupdate_worksheetget_timebatch_delete_recordscreate_roleget_role_detailsget_workflow_detailscreate_recordbatch_create_recordsupdate_recordget_workflow_listget_regionsfind_departmentget_record_logsget_app_infobatch_update_recordsremove_member_from_roleget_record_share_linkdelete_roledelete_recordget_role_listfind_memberleave_all_rolesget_worksheet_structuredelete_optionsetget_record_listget_record_pivot_datacreate_optionsetget_record_detailsget_optionset_listcreate_worksheetadd_member_to_roleupdate_optionset

    Fix: Review and remediate the identified issue.

  • InfoAS-010

    🔑Insecure Secret Handling

    get_record_share_link:input parameter "password" accepts a credential (informational; not evidence of insecure handling)

    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 garfield-bb-hap-paas2025"

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 B](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-b.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)